Skip to main content
Glama

refund_run

DestructiveIdempotent

Provider refunds a successful or disputed execution to resolve it. Trial credits are returned once; already accepted payouts are final.

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": {
      "run_id": "<run_id>"
    },
    "name": "refund_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds genuinely new context by marking the boundary of reversibility (accepted payouts are final) and the one-time nature of trial credit returns. It does not mention authorization requirements or the failure/error behavior of a rejected refund, keeping it from a 5.

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?

Two tight sentences with no filler; the core effect is front-loaded and the irreversibility caveat follows immediately. Every clause carries operational meaning.

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 destructive, open-world mutation with no output schema and one parameter, the description covers what the tool does and the key irreversibility caveat. It leaves some gaps around authorization and error outcomes, but an agent can call it correctly from this text plus the annotations.

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?

There is a single parameter, run_id, with 0% schema description coverage, and the description never mentions it. Its meaning is self-evident from the name, but the description could have clarified that the ID must refer to a successful or disputed execution rather than any run.

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 verb and resource: the provider refunds a successful or disputed execution to resolve it. That distinguishes it from siblings like complete_run or fail_run by naming the resolution action. It stops short of explicitly contrasting with dispute_run or cancel_run, which are the nearest alternatives.

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?

The second sentence supplies an implicit eligibility rule: trial credits can be refunded once, but already accepted payouts are final, so the agent knows one case where the tool must not be used. There is no explicit statement of when to choose this over dispute_run or cancel_run, and no stated caller role beyond the word 'Provider'.

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.

Resources