Skip to main content
Glama

retry_payment

Request approval to retry a refused payment for the original accepted quote by supplying the batch ID.

Instructions

Request approval to retry a refused payment for the original accepted quote.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "retry_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
batch_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that this is an approval request rather than an immediate retry, but it omits critical details such as permissions, whether approval triggers an automatic retry, idempotency, and financial side effects.

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?

The description is a single front-loaded sentence with no redundant wording. It efficiently conveys the core action and context without unnecessary padding.

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?

For a payment-related mutation with no annotations, no output schema, and 0% schema description coverage, the description is too sparse. It should clarify parameter meanings, approval flow behavior, and what an agent should expect after invoking the tool.

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 explain both parameters. It indirectly hints that 'batch_id' relates to the original accepted quote, but it never mentions the parameter by name and gives no meaning at all for 'confirm.'

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 specific action: requesting approval to retry a refused payment tied to an original accepted quote. It clearly distinguishes this from the unrelated sibling tools, though it leaves some ambiguity about whether the tool performs the retry or only initiates an approval workflow.

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 implied by 'refused payment' and 'original accepted quote,' suggesting the tool applies only to previously refused payments with an existing accepted quote. However, it does not state explicit preconditions, exclusions, or alternatives to consider.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.