Skip to main content
Glama

import_payroll_employees

Import employees from the filled-in template (get_payroll_employee_import_template, .xlsx/.csv). All or nothing; existing employee_no rows are skipped. dry_run only reports. file_base64 is the file's raw bytes, base64.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>",
      "filename": "<filename>",
      "file_base64": "<file_base64>"
    },
    "name": "import_payroll_employees"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
filenameYes
company_idYes
file_base64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: all-or-nothing atomicity, that existing ``employee_no`` rows are skipped (dedup/idempotency), and that dry_run is report-only. It omits error semantics, required permissions, and what a successful run returns, which matters for a write tool with no output schema.

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

Conciseness5/5

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

Four short clauses, front-loaded with the source-template constraint, then the atomicity rule, then the two behavioral flags. No filler and nothing buried mid-paragraph despite the telegraphic style.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description covers the highest-risk unknowns: atomicity, silent skipping of existing rows, and safe preview via dry_run. Remaining gaps are the two unexplained parameters and the shape of the import report, which keep it from being fully self-sufficient.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and only partly does. It usefully explains `file_base64` (raw bytes, base64-encoded) and `dry_run` (reports only), but `company_id` and `filename` — including whether the extension must match the template format — are left entirely undocumented.

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

Purpose4/5

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

States a specific verb and resource ("Import employees") and pins the source artifact to the companion template tool (``get_payroll_employee_import_template``, .xlsx/.csv). An agent can tell this is the payroll-employee ingestion path, though it never explicitly contrasts with the lookalike sibling `upload_accounting_import`.

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

Usage Guidelines4/5

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

Usage context is clear: the file must come from the named template tool, and `dry_run` "only reports" which implies a validate-then-commit flow. There are no explicit exclusions or prerequisites (permissions, company scope), so it stops short of a full when/when-not map.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources