Skip to main content
Glama

Excess Cash Sweep

bpj_excess_cash_sweep
Read-onlyIdempotent

Preserve a minimum operating cash reserve and apply the agreed share of excess cash against eligible debt.

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": {
      "cash": "<cash>",
      "floor": "<floor>",
      "debtBalance": "<debtBalance>",
      "sweep": "<sweep>"
    },
    "name": "bpj_excess_cash_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
cashYes
floorYes
sweepYes
debtBalanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 fully covered. The description adds only the conceptual mechanics (floor preserved, percentage of excess applied to eligible debt) and says nothing about what is returned or how the result is capped by the debt balance.

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 with no filler; the core rule is stated first. It is efficient but leaves room for a second short sentence on inputs or output at little cost.

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?

This is a pure computation tool with four required numeric inputs and no output schema, so the description should state the return value (swept amount, remaining cash, etc.). It does not, leaving the agent unsure what the result represents in addition to the partially specified parameter meanings.

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 carries the burden of explaining the four required inputs. It does map conceptually onto all four ('minimum operating cash reserve' for floor, 'excess cash' for cash minus floor, 'agreed share' for sweep, 'eligible debt' for debtBalance), but it omits units (sweep is a percentage), the formula, and the cap against debtBalance, so the compensation is partial.

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 concrete operation (preserve a cash floor, apply a share of the excess against debt) rather than restating the title, so an agent can tell it is an excess-cash/debt sweep calculation. It distinguishes itself implicitly from adjacent treasury tools like bpj_cash_runway or bpj_free_cash_after_capex, though it never names an alternative explicitly.

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 guidance, no exclusions, and no mention of prerequisites (e.g., sweep should not exceed the debt balance). The agent must infer from the single sentence that this is the right tool to call for a sweep computation rather than a reporting tool.

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.