Skip to main content
Glama

create_payroll_export

DestructiveIdempotent

Create a payroll export from approved entries and lock those revisions. Show the owner the selected entries and payroll codes before proceeding. Reuse the same export ID and inputs for an identical retry.

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": {
      "id": "<id>",
      "entries": "<entries>",
      "employees": "<employees>"
    },
    "name": "create_payroll_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entriesYes
employeesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds the concrete consequence — source revisions get locked — and specifies that an identical retry must reuse the same export ID and inputs. It does not cover permissions or entry limits, so it is strong rather than complete.

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?

Three sentences, each doing distinct work: what it creates, the pre-flight confirmation, and retry semantics. The primary action and its side effect are front-loaded with no filler.

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 destructive, idempotent mutation with no output schema and three required params, the description covers the main risk (locking revisions), the confirmation step, and retry behavior. Missing permission requirements and the nested-entry limits keep it just shy of complete.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the burden. It maps loosely onto all three params (export 'id', 'selected entries', 'payroll codes'), but never explains the per-entry 'revision' field, the staffId-to-code pairing in 'employees', or the 100-item caps.

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 ('Create a payroll export') plus the source constraint ('from approved entries') and a side effect ('lock those revisions'). This clearly separates it from the retrieval sibling get_payroll_export, though no sibling is named explicitly.

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?

Gives real preconditions: entries must be approved, and the owner should be shown the selected entries and payroll codes before proceeding. The retry sentence tells the agent how to repeat safely. It stops short of naming alternatives or stating when not to call it.

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