Skip to main content
Glama

Taokeh MCP server

by my.taokeh
OverviewAdmin

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 ONLY: payroll sits behind its own role in Taokeh and this tool refuses on any other connection. 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. Dates show when Glama detected each change.

  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.8/5.0
Behavior5/5

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

The readOnlyHint is reinforced and expanded: the tool 'cannot create a run, pay anybody, or file anything.' It also discloses behavioral edge cases: it reads the latest FINALIZED or POSTED run, returns a plain statement if nothing has been run rather than zeros, and enforces an ADMIN ONLY role requirement. These go far beyond the annotations.

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 every sentence adds functional or safety-relevant information, and the most important user-facing behavior is front-loaded. The final ADMIN/READ-ONLY warning is appropriately placed at the end.

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 read-only summary tool with no output schema, the description comprehensively covers return semantics, parameter behavior, permission constraints, and edge cases. The only missing piece is exact response structure, but that is unnecessary given the detailed narrative and the tool's simple boolean/string parameters.

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

Parameters4/5

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

Schema coverage is only 33% because month and perEmployee lack schema descriptions, but the description compensates thoroughly: month format YYYY-MM and behavior when omitted, perEmployee's sensitivity and employeeId detail, and staff's independent-of-run behavior and link to update_employee_draft. Only a small amount of redundancy with the staff schema description remains.

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 names a specific verb and resource ('A month's payroll...') and enumerates exactly what is included: gross, deductions, employer contributions, net pay, and true total cost. It also distinguishes itself from sibling tools by clarifying payroll-specific outputs and pointing to update_employee_draft for employee IDs.

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 explicitly tells when to use it ('what does payroll look like this month' and 'who is out next week'), when to set perEmployee and staff, and warns to request per-employee salaries only when genuinely needed. It also contrasts with alternatives like employer_cost_estimate by clarifying this is actual stored payroll, not a recalculation.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources