Skip to main content
Glama

dispute_run

Buyer disputes successful output before acceptance and before the review deadline. Provider can refund immediately; buyer can claim refund at the deadline. No independent adjudicator.

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

Input Schema

NameRequiredDescriptionDefault
reasonNoQuality dispute reason
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower. The description still adds genuine behavioral context the annotations cannot: the two settlement paths (provider refunds immediately vs. buyer claims at the deadline) and the explicit absence of an adjudicator, which tells the agent this is a bilateral, deadline-driven mechanism rather than an arbitration request.

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 short sentences, zero waste: eligibility window first, then the two outcome branches, then the structural caveat. Every clause contributes a distinct fact and nothing is repeated from the annotations or schema.

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 non-idempotent mutation with no output schema, the description covers eligibility and the two settlement branches but omits what the call itself returns, what state the run enters after a dispute (frozen, pending refund, still acceptable?), and whether the dispute blocks a competing accept_run. Those are the gaps an agent would hit immediately on invocation.

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 50%: 'reason' is documented in the schema, while 'run_id' has only a length constraint and no semantic note. The description never mentions either parameter, so it neither reinforces run_id's role as the disputed run nor suggests what belongs in the free-text reason. At this coverage level the schema carries the load, and the description adds nothing, which is the baseline 3 rather than a lift.

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?

States a specific verb (disputes) against a specific object (successful output) scoped to the buyer and to a window before acceptance and before the review deadline. That framing implicitly separates it from dispute_delivery (which concerns the delivery step rather than accepted output), but it never names or contrasts a sibling outright, so the agent must infer the boundary.

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 timing preconditions ('before acceptance and before the review deadline') give real when-to-use guidance, which is the strongest part. There is no explicit when-not guidance and no pointer to alternatives such as dispute_delivery, refund_run, or cancel_run when the window has already closed, leaving escalation paths to inference.

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