Skip to main content
Glama

Headcount Turnover Reconciliation

bpj_headcount_turnover_reconciliation
Read-onlyIdempotent

Reconcile closing headcount to hires and departures and calculate period turnover using average opening and closing headcount.

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": {
      "start": "<start>",
      "end": "<end>",
      "exits": "<exits>"
    },
    "name": "bpj_headcount_turnover_reconciliation"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
exitsYes
startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine methodological detail — turnover is computed on the average of opening and closing headcount — but does not state what the reconciliation result looks like or how discrepancies are reported, and there is no output schema to compensate.

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?

A single front-loaded sentence with no filler, stating both the reconciliation and the turnover basis. It is dense but well-structured; only the unexplained 'hires' term costs it a point.

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

Completeness3/5

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

For a closed-world calculation tool with three required params and no output schema, the description should say what is returned (turnover rate? variance check? pass/fail?) and it does not. It covers the inputs adequately but leaves the result shape entirely unspecified.

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 description coverage is 0%, but the description effectively maps all three inputs (opening headcount → start, closing headcount → end, departures → exits) and explains the derived relationship via hires. It stops short of clarifying that hires are implicit rather than supplied, or any unit/edge-case conventions.

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?

Names specific verbs (reconcile, calculate) and resources (closing headcount, turnover), so the agent knows this is a headcount-roll-forward plus turnover computation. The reference to 'hires' is slightly confusing since no hires parameter exists, but the core purpose is unmistakable.

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

Usage Guidelines3/5

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

The description implies usage (period headcount reconciliation and turnover), but gives no explicit when-to-use, no prerequisites, and no pointer away from the related sibling bpj_headcount_hiring_gap. An agent must infer the boundary from the description alone.

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.