Skip to main content
Glama

Vacancy Contribution Drag

bpj_vacancy_contribution_drag
Read-onlyIdempotent

Combine vacant role-days and their daily contribution gap with direct recruiting expense to estimate vacancy impact.

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": {
      "vacancy": "<vacancy>",
      "days": "<days>",
      "daily": "<daily>",
      "recruited": "<recruited>"
    },
    "name": "bpj_vacancy_contribution_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
dailyYes
vacancyYes
recruitedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world calculation, so the safety profile is covered. The description adds the behavioral fact that it combines three vacancy-related inputs with recruiting expense to estimate impact, but says nothing about the exact formula, output shape, or assumptions.

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 definition is a single efficient sentence with no filler and the core operation is front-loaded. It is appropriately sized for a simple calculator, though the structure could be slightly improved by explicitly naming the output.

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

Completeness2/5

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

For a four-parameter calculation tool with no output schema and 0% schema description coverage, the description does not specify the exact calculation or return value. An agent knows the general intent but lacks enough detail to invoke the tool confidently and interpret its result.

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 compensate for all four parameters. It loosely maps 'vacant role-days' and 'daily contribution gap' to the vacancy, days, and daily inputs and 'direct recruiting expense' to recruited, but it does not clarify units, the exact multiplication/summation formula, or how 'average days open' is meant to be applied.

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 uses a specific verb ('Combine') and names the exact inputs and the intended output ('estimate vacancy impact'). It clearly identifies a calculation tool and distinguishes it from general HR or finance tools, though it does not explicitly name a sibling alternative.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The formula-like phrasing implies a calculation use case, but an agent must infer the context on its own.

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.