Skip to main content
Glama

Capped Leave Accrual

bpj_capped_leave_accrual
Read-onlyIdempotent

Accrue leave and deduct hours used before applying a closing carry cap, reporting any forfeited hours.

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": {
      "leave": "<leave>",
      "accrue": "<accrue>",
      "periods": "<periods>",
      "used": "<used>",
      "cap": "<cap>"
    },
    "name": "bpj_capped_leave_accrual"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
usedYes
leaveYes
accrueYes
periodsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive calculation, so the safety profile is covered. The description adds real behavioral content beyond that: the operation order (accrue, then deduct used, then cap) and the fact that excess hours are forfeited and reported. It does not state units or rounding of the reported forfeiture, which keeps it at 4.

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?

One dense sentence, front-loaded with the action and ordered left-to-right through the calculation. Nothing is padded, though the compression leaves the opening-balance parameter unmentioned.

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 five-parameter, all-required calculation with no output schema, the description should pin down the formula and the shape of the result. It explains the cap/forfeiture semantics well but never states how opening leave interacts with accrued periods, nor whether the forfeiture is returned in hours. Adequate, not 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 must compensate; it partially does by naming 'used' and the closing 'cap' and by implying accrue x periods. However, 'leave' (opening hours) is not referenced, and the exact arithmetic relationship among leave, accrue, periods, and used is left to inference. Schema titles carry some of the burden, so 3 rather than lower.

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 computation: accrue leave, deduct used hours, apply a closing carry cap, and report forfeitures. That is a distinct verb+resource combination an agent can recognize. It does not name any sibling (e.g. bpj_leave_payout_liability) to differentiate itself, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance and no named alternative among the many leave/accrual siblings. The ordering of operations implies a payroll-style calc, but an agent must infer the scenario 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.