Skip to main content
Glama

Headcount Hiring Gap

bpj_headcount_hiring_gap
Read-onlyIdempotent

Reconcile starting headcount, forecast exits and net transfers against a target to identify external hiring needs or excess positions.

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>",
      "departures": "<departures>",
      "transfers": "<transfers>",
      "target": "<target>"
    },
    "name": "bpj_headcount_hiring_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
targetYes
transfersYes
departuresYes

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the analytical intent but omits behaviorally important details such as the underlying formula, whether the gap is signed (positive = hiring need vs excess), and units – all of which matter for interpreting output.

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 dense sentence with an input-to-outcome structure and no filler; the purpose is front-loaded. It could be marginally better if the computation order were broken out, but nothing is wasted.

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 four-required-parameter read-only calculation with no output schema and no nested structures, the description conveys both inputs and the meaning of the result. The remaining gap – the exact arithmetic and sign convention – is the main thing an agent would still have to guess.

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 burden falls on the description, which does map its four concepts onto the four parameters ('forecast exits', 'net transfers' vs the schema's expected departures and confirmed net internal transfers). However, it does not explain the allowed negative range on transfers or how a negative gap should be read, so compensation for the coverage gap is only partial.

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?

The description names a specific verb ('Reconcile') plus the exact inputs (starting headcount, forecast exits, net transfers, target) and the decision it supports ('external hiring needs or excess positions'), which is far more specific than the title alone. It does not, however, explicitly distinguish itself from the similarly named sibling bpj_headcount_turnover_reconciliation, leaving that distinction implicit.

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?

Usage is only implied by the stated outcome – an agent can infer this is a workforce-planning reconciliation, but there is no explicit statement of when to prefer this tool over the turnover reconciliation sibling, nor any prerequisites or exclusions. That is adequate context but no real routing guidance.

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.