Skip to main content
Glama

Project Commitment Headroom

bpj_project_commitment_headroom
Read-onlyIdempotent

Update the baseline for approved changes and deduct booked costs and non-overlapping open commitments to calculate remaining headroom.

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": {
      "baselineCost": "<baselineCost>",
      "approved": "<approved>",
      "actual": "<actual>",
      "committed": "<committed>"
    },
    "name": "bpj_project_commitment_headroom"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualYes
approvedYes
committedYes
baselineCostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 the computational behavior (baseline is adjusted, costs and commitments are deducted), but the phrasing 'Update the baseline' is slightly ambiguous for a pure read operation and no output shape, currency, or rounding behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no filler, but it is a dense compound construction ('Update ... and deduct ... to calculate') whose ordering is awkward for such a simple four-input calculation. It is front-loaded on the operation rather than the purpose.

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-form calculator with four required numeric inputs and no output schema, the definition should spell out the arithmetic and the meaning/units of the returned headroom. It conveys the general flow but not the exact formula or return semantics, leaving moderate gaps.

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%, so the description must carry the load and it does map each input conceptually: baselineCost ('the baseline'), approved ('approved changes'), actual ('booked costs'), committed ('open commitments'). It stops short of clarifying that approved may be negative or that committed excludes booked costs, leaving that to the schema titles.

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 ('calculate remaining headroom') and enumerates the ingredients it combines (baseline, approved changes, booked costs, open commitments), so the resource is identifiable. It never distinguishes itself from nearby financial siblings such as bpj_interest_service_headroom or bpj_usage_commitment_true_up, so it falls 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 Guidelines3/5

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

Usage is only implied: the wording suggests a headroom check on an approved baseline, but there is no statement of when to call this versus the other headroom/true-up tools, and no preconditions (e.g., that approved changes may be negative, or that commitments must exclude already-booked costs).

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.