This article explains what your assistant can do in Teamso. You do not need to know the tool names: you ask the assistant in plain language and it decides which tool to call. The tables show what you can ask for and the tool used for it.
The hosted server and the Teamso MCP package (1.3.0 and later) offer the same 37 tools. Which ones you can use depends on your role and permissions in Teamso.
Before you start
Your assistant must be connected to Teamso (Overview).
Tools marked as changing records need the same permission as the matching action on screen.
Step by step: tools
Help
Searches the Teamso how-to guides. It does not touch your Teamso account; it reads the public guides.
What you can ask for | Tool | Changes records |
Searching the guides for a question such as "How do I enter an overtime request?" (can be filtered by module and role) |
| No |
Reading a whole guide with its steps |
| No |
Seeing the modules that have guides and their article titles |
| No |
Account
What you can ask for | Tool | Changes records |
Seeing your name, company, department and position, manager, roles and permission codes |
| No |
Leave
Creating and cancelling a leave request is confirmed with an SMS code sent to your phone: the code is valid for 3 minutes and the operation uses Digital Credits as in the web app.
What you can ask for | Tool | Changes records |
Seeing the leave types you can request and the remaining balance of each |
| No |
Seeing a summary of your leave balance (remaining days per type) |
| No |
Calculating how many working days a date range takes and the return-to-work date (using your working calendar and public holidays) |
| No |
Sending a confirmation code to your phone |
| Sends an SMS |
Creating a leave request with the SMS code and sending it for approval |
| Yes |
Listing your own leave requests by date and status |
| No |
Cancelling a leave request with the SMS code (needs the leave delete permission) |
| Yes |
Approvals
What you can ask for | Tool | Changes records |
Seeing the leave requests waiting for your approval |
| No |
Approving a request at your approval step, or rejecting it with a reason |
| Yes |
Employees
Only employees you are allowed to see on screen.
What you can ask for | Tool | Changes records |
Finding active colleagues by name or email (without access to the company directory it searches the employees you are responsible for) |
| No |
Seeing a colleague's branch, department, position, manager and contact details (the phone number is masked unless you may read it) |
| No |
Performance
Goals are linked to a period by its name; the assistant lists the periods first.
What you can ask for | Tool | Changes records |
Seeing the performance periods, goal entry windows and the evaluation scale |
| No |
Seeing your goals in a period |
| No |
Seeing the goals of the employees you manage and the approvals you can give |
| No |
Adding a draft goal for yourself or a direct report |
| Yes |
Sending your draft goals to your manager for approval |
| Yes |
Approving a goal that is waiting for approval |
| Yes |
Revising a goal (name, description, weight, target) and approving it |
| Yes |
Entering the actual value of your goal during evaluation |
| Yes |
Entering the actual value of an employee's goal as their manager |
| Yes |
Approving an employee's evaluation for the period at your approval step |
| Yes |
Badges
Every rule of the screen applies when giving a badge: who may give which badge to whom, the per-person limit, the days before giving again, approval and the monthly peer quota. The assistant finds the person with search_employees and asks you to confirm the badge, the person and the message (Giving badges).
What you can ask for | Tool | Changes records |
Seeing the badges you can give, your giving role and the peer quota left |
| No |
Giving a badge with a message to one or more colleagues ("Give Ayşe the Team Player badge") |
| Yes |
Seeing the badges you received, who gave them and the message |
| No |
Communication
What you can ask for | Tool | Changes records |
Seeing the company and shuttle announcements visible to you, newest first |
| No |
Payroll
Only your own payslips.
What you can ask for | Tool | Changes records |
Seeing your e-payslips and their status by month or year |
| No |
Opening a payslip PDF |
| No |
All modules
Tasks the tools above do not cover (expenses, requests, overtime, time tracking, recruiting, inventory, settings...) go through the generic API tools. Only the actions your permissions allow are listed; the write tool shows a preview first and runs only after you agree.
What you can ask for | Tool | Changes records |
Searching the available actions by keyword, module or effect |
| No |
Seeing the modules you can use |
| No |
Seeing what an action needs |
| No |
Reading data (e.g. your expenses this month) |
| No |
Adding, changing or deleting records after you agree |
| Yes |
Sending a code to your phone for an action that needs an SMS code |
| Sends an SMS |
Step by step: ready-made prompts
Ready-made prompts (MCP prompts) are starting points that your client shows as slash commands or in a prompt picker. A prompt only steers the assistant through the tools: every write step still needs your confirmation, and a leave request still needs the SMS code.
Prompt | What it does | Inputs |
| Picks the leave type, shows the working days and the remaining balance, asks you to confirm, then sends the request with the SMS code. Missing dates are asked for. | Start, end, leave type and a note for the approver; all optional. An empty end means the same day as start, an empty type means annual leave. Relative dates such as "tomorrow" are resolved in Turkey time. |
| Lists the leave requests waiting for your approval as a table and asks you, request by request, whether to approve or reject; it never decides for you. A rejection needs a reason. | None. |
Result
The assistant calls these tools on your behalf. What you cannot do on screen you cannot do with a tool either, and some sensitive operations are never available with a token (Security and permissions). Actions taken by the assistant go through the same approval flows as on screen and produce the same notifications.
Common problems
Symptom: The assistant says it cannot do something because there is no tool for it.
Cause: Your connection serves only some tool groups (TEAMSO_TOOLSETS or ?toolsets= in the address), or you do not have the permission for that action.
Solution: Remove the tool groups or add the one you need (e.g. badges for badges). Without the permission, leave the task to someone who has it; you can ask the assistant how it is done, it searches the guides.
Symptom: My team's goals or the pending requests come back empty.
Cause: No record is at your approval step, or you have no manager permission.
Solution: Check the same list on screen (Approving a leave request, Team goals as a manager).


