Skip to main content
Glama

Project Contingency Draw Review

bpj_contingency_draw_review
Read-onlyIdempotent

Reconcile an approved contingency reserve with previous draws and determine coverage for a proposed draw.

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": {
      "reserve": "<reserve>",
      "draws": "<draws>",
      "pending": "<pending>"
    },
    "name": "bpj_contingency_draw_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
drawsYes
pendingYes
reserveYes

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, closed-world, so the safety profile is fully covered by structured data. The description adds that the operation reconciles inputs against a reserve, which is useful behavioral context, but says nothing about edge cases (e.g., draws already exceeding reserve) or what is returned — notable given there is no output schema.

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 covering the operation and its inputs, with no filler. It is efficient but arguably too terse for a definition carrying a documentation gap.

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

Completeness5/5

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

Placeholder

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 schema supplies only bare titles, and the description does map its nouns onto the three parameters ('approved contingency reserve' to reserve, 'previous draws' to draws, 'proposed draw' to pending). It adds real meaning over the field titles but no units, currency assumptions, or sign conventions, leaving some interpretive burden.

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?

States a specific verb ('reconcile') and named resources (approved contingency reserve, previous draws, proposed draw), so an agent knows it is a reconciliation/coverage computation. It does not differentiate itself from any sibling, and with a large unrelated sibling catalog it leaves that routing to the names alone.

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?

The description gives no when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives. The phrase 'proposed draw' only weakly implies the decision context (evaluating a draw request before approval).

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.