Skip to main content
Glama

accept_run

DestructiveIdempotent

Buyer accepts verified successful output, releasing trial credits once. Seller may settle an undisputed success after its disclosed 24-hour review deadline. Final settlement; schema validation is not quality approval.

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": "accept_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare a destructive, non-read-only, idempotent operation, and the description usefully adds that settlement is final and that credits are released exactly once. It does not state what state the run moves into, what permissions or role checks are enforced, or what a failed call looks like, so the added behavioral detail is real but partial.

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?

Three compact sentences, front-loaded with the actor and effect, then timing, then the finality caveat. Nothing is redundant and the qualifier 'schema validation is not quality approval' earns its place by heading off a plausible misinterpretation.

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?

For a one-parameter destructive settlement tool with no output schema, the definition covers consequence, timing and finality, which is close to sufficient. It leaves gaps around post-acceptance run state, authorization requirements, and the contested/dispute path an agent may need to choose between.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only run_id is accepted and the schema constrains its length, so parameter documentation is largely self-evident and the description need not restate it. The description adds no extra meaning about run_id itself, but with a single unambiguous identifier the schema carries the burden adequately.

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 action and object ('Buyer accepts verified successful output') plus the economic consequence ('releasing trial credits once'), so an agent knows this is a settlement step on a run, not a generic state change. It stops short of differentiating itself from near-name siblings such as accept_delivery or complete_run.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete usage contexts: a buyer accepting verified successful output, and a seller settling an undisputed success after the disclosed 24-hour review deadline. There is no explicit when-not-to-use clause or pointer to an alternative path (e.g. dispute_run) for contested outcomes.

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