Skip to main content
Glama

fail_run

Provider ends a live claimed execution as failed and refunds its reserved trial credits once.

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>",
      "claim_token": "<claim_token>"
    },
    "name": "fail_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoFailure reason without secrets
run_idYes
claim_tokenYesShort-lived run-scoped claim token returned by claim_run; keep private

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 non-read-only, non-idempotent, open-world, non-destructive. The description adds value beyond that by disclosing the trial-credit refund and that it happens exactly once, which materially informs the agent about a consequential, non-repeatable side effect. It omits permission requirements, what happens on repeated calls, and what a successfully failed run returns.

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 dense sentence with no filler, front-loading the actor, the state transition, and the credit-refund consequence. Nothing is wasted and no reordering would improve scanability.

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 three-parameter mutation tool with no output schema, the description covers the actor, precondition, terminal state, and the financial side effect — the key things an agent needs before invoking. Minor gaps remain around authorization and post-call state (e.g., whether the claim_token becomes unusable), but nothing critical is missing.

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 coverage is 67%: claim_token and reason carry descriptions (private, short-lived, 'without secrets'), while run_id is undocumented but self-evident. The description only reinforces that the run must be a live claimed execution, adding little beyond the schema, so the baseline 3 fits.

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 outcome ('ends a live claimed execution as failed') plus the side effect ('refunds its reserved trial credits once'), which cleanly separates it from complete_run, cancel_run, and refund_run. It does not name any sibling explicitly, so the differentiation must be inferred from behavior rather than stated.

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?

Implied guidance is present: the caller must be the 'Provider' and the execution must be 'live' and 'claimed', which narrows when this applies. However, there is no explicit when-not condition and no named alternative for related cases such as cancel_run or dispute_run, leaving the agent to infer routing.

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