Skip to main content
Glama

Renewal Book and Cash Check

bpj_renewal_book_cash_check
Read-onlyIdempotent

Compare renewal completion by contract count with collection of the amount due and show the unpaid balance.

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": {
      "contracts": "<contracts>",
      "renewed": "<renewed>",
      "due": "<due>",
      "received": "<received>"
    },
    "name": "bpj_renewal_book_cash_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueYes
renewedYes
receivedYes
contractsYes

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?

Annotations already declare this a read-only, idempotent, non-destructive, closed-world computation, so the safety profile is covered. The description adds that the result includes an unpaid balance, but it does not disclose edge-case behavior—notably that 'due' may be 0, which makes any collection-percentage calculation undefined.

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 sentence with no filler and the core comparison front-loaded. It is slightly compressed to the point of ambiguity ('collection of the amount due'), but nothing is redundant.

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?

There is no output schema, so the description carries full responsibility for describing the return value, yet it only says 'show the unpaid balance' without saying whether a renewal rate, a collection ratio, or a variance is also returned. For a four-required-input computation with zero schema documentation, that leaves real gaps.

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, and it only partially does. It implicitly maps the four inputs (contracts, renewed, due, received) but never states units, currency, whether amounts are in major or minor units, or how 'renewed' relates to 'contracts'.

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 states a concrete computation: comparing renewal completion by contract count against cash collected on the amount due, plus the unpaid balance. It is clear what the tool does, but it never distinguishes itself from similarly named finance/check siblings such as bpj_cash_conversion_cycle or bpj_bank_book_reconciliation.

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, no prerequisites (e.g., that all four inputs must come from the same renewal cohort), and no mention of alternatives. The agent must infer usage entirely from the name and parameter titles.

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.