Skip to main content
Glama

Payment Retry Recovery

bpj_billing_retry_recovery
Read-onlyIdempotent

Estimate expected recovered payments and cash across two retries, applying the second rate only to first-round failures.

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": {
      "failures": "<failures>",
      "first": "<first>",
      "next": "<next>",
      "ticket": "<ticket>"
    },
    "name": "bpj_billing_retry_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextYes
firstYes
ticketYes
failuresYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is fully covered elsewhere. The description adds the calculation model (second rate applied only to first-round failures), which is genuinely useful, but stays silent on return shape, rounding, and whether 'payments' is a count or an amount.

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 sentence with no filler, front-loading the output ('expected recovered payments and cash') ahead of the one qualifying rule. Every clause carries information.

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?

With four required numeric parameters and no output schema, the description does enough to explain the computation but not the result: it never says what the returned values look like or in what units cash is expressed. Adequate for a simple calculator, but an agent would still guess at the output contract.

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?

The schema titles already label each parameter (initially failed payments, first retry recovery %, second retry recovery on remaining failures %, mean failed charge), and the description's key contribution is clarifying the compounding rule that the second rate applies only to first-round failures — a non-obvious semantic worth having. It still says nothing about units of the cash output or how the mean charge combines with counts, leaving gaps at 0% schema description coverage.

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 verb ('Estimate') and a specific output ('expected recovered payments and cash'), plus the two-stage retry structure, so an agent knows this is a modeling/forecast tool rather than a data lookup. It does not explicitly contrast itself with related siblings like bpj_interpret_retry_after or bpj_system_retry_amplification, so it stops short of full differentiation.

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 statement of when to use this tool, when not to, or which sibling to reach for instead. The agent must infer from the description that this is a two-stage recovery forecast rather than a live retry-status or timing 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.