Skip to main content
Glama

Collection Float Release

bpj_collection_float_release
Read-onlyIdempotent

Estimate cash released by shortening collection float and annual financing savings at the supplied borrowing rate.

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": {
      "receipts": "<receipts>",
      "freed": "<freed>",
      "nominal": "<nominal>"
    },
    "name": "bpj_collection_float_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
freedYes
nominalYes
receiptsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered for the agent. The description adds that the tool produces two distinct estimate quantities, but omits the computation basis (e.g. whether savings is linear in days-saved times receipts times rate) and any output units, so it goes only slightly beyond the annotations.

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

Conciseness5/5

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

A single compact sentence with the two outputs front-loaded and no filler or restated name. Nothing could be trimmed without losing content.

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

Completeness4/5

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

For a simple three-parameter, closed-form calculator with no output schema, the description identifies both returned quantities, which is close to sufficient. The remaining gap is that it never specifies return units or formatting, which an agent would need since there is no output schema to consult.

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 carry the semantic load, and it does so only partly: 'shortening collection float' maps to the ambiguously named 'freed' param and 'borrowing rate' maps to 'nominal'. The third parameter, daily clearing receipts, is never referenced in the description, and no units (days vs. fraction, percent vs. decimal) are clarified beyond what the schema titles already say.

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 gives a specific verb ('Estimate') and two concrete outputs: cash released from shortening collection float and annual financing savings. That is enough to distinguish this calculation tool from the release-engineering siblings, though it never states the domain explicitly (receivables/treasury), leaving the agent to infer it from parameter titles.

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: an agent can infer it should call this when it wants a float-release estimate at a given borrowing rate. There is no statement of when not to use it, no prerequisites, and no named alternative among the many bpj_* financial calculators.

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.