Skip to main content
Glama

Taokeh MCP server

by my.taokeh
OverviewDiscussionsAdmin

Payroll summary

payroll_summary
Read-only

A month's payroll from gross to net, as it was actually run: total gross (basic, allowances, overtime, public-holiday pay and any bonus), what was deducted from staff (EPF, SOCSO, EIS, SKBBK, PCB/MTD, zakat), what the employer contributed on top (EPF, SOCSO, EIS, HRD Corp levy), the total net pay, and the employer's TRUE total cost for the month — wages plus every employer contribution. Also lists who is on approved leave in the next 14 days, so "what does payroll look like this month" and "who is out next week" are one call. With no month it reads the latest FINALIZED or POSTED run; give a month as YYYY-MM for a specific one. Set perEmployee: true for the per-person breakdown — those are individual salaries, so ask for them only when the user actually wants them; each entry carries that person's real employeeId. Set staff: true for the full employee ROSTER with ids, which works even when payroll has never been run — that is where the employeeId for update_employee_draft comes from, and it is the only place an id is published: never key an employee by name. Every figure is a sum of the STORED payslips of that run — the same numbers the staff were paid on and the payroll journal was posted from — never a recalculation. If nothing has been run, it says so plainly rather than returning a month of zeros. ADMIN AND BOOKKEEPER + PAYROLL ONLY: payroll sits behind its own role in Taokeh and this tool refuses on any other connection (a plain Bookkeeper included). READ-ONLY — it cannot create a run, pay anybody, or file anything with LHDN, KWSP or PERKESO.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthNo
staffNoReturn the full employee ROSTER (id, name, staff no., status, designation, basic salary) alongside the summary — independent of any run, so it works even before the first payroll. This is where the employeeId for update_employee_draft comes from. Individual salaries: ask for it only when the user actually needs it.
perEmployeeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / staff
      Added value: +{
+  "description": "Return the full employee ROSTER (id, name, staff no., status, designation, basic salary) alongside the summary — independent of any run, so it works even before the first payroll. This is where the employeeId for update_employee_draft comes from. Individual salaries: ask for it only when the user actually needs it.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation, the description discloses that it is read-only and cannot create runs or file with authorities, that it reads from stored payslips (never recalculation), that it returns leave data, and that it states plainly when no run exists instead of returning zeros. It also notes the tool refuses non-payroll connections. These are substantial behavioral disclosures that enrich the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but densely packed with essential information, and it is well-structured: it opens with the core output, then covers parameters, data source, and permissions. Every sentence adds value; however, it could be trimmed slightly without losing critical detail, making it a 4 rather than a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three optional parameters, no output schema, and a read-only annotation, the description is remarkably complete. It covers what the output includes, how to handle month, the purpose and sensitivity of perEmployee, how to obtain employee IDs for update_employee_draft, the data source (stored payslips), edge cases (no run), and role-based access. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (staff has a description; month and perEmployee do not). The description compensates fully: month is explained with format and default behavior, perEmployee is explained as sensitive and carrying real employee IDs, and staff is elaborated with its purpose for obtaining employee IDs. This goes well beyond the schema to clarify each parameter's semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a full payroll summary from gross to net, including contributions, net pay, employer cost, and also lists upcoming approved leave. It distinguishes itself from other financial tools by specifying the exact components and the one-call capability for two distinct queries, and it explicitly references the sibling update_employee_draft for employee ID sourcing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool ('what does payroll look like this month' and 'who is out next week'), how the month parameter behaves (latest run if omitted, YYYY-MM for specific), and when to set perEmployee and staff flags, including a warning that perEmployee returns sensitive individual salaries. It also specifies role restrictions (ADMIN AND BOOKKEEPER + PAYROLL ONLY) and that it refuses other connections, providing clear guidance on appropriate invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Taokeh MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources