Skip to main content
Glama

Open a dispute

open_dispute

Funds stay held; ops reviews within 24h.

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": {
      "delivery_id": "<delivery_id>",
      "reason": "<reason>"
    },
    "name": "open_dispute"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
evidenceNo
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations only declare the generic profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description usefully adds that funds remain held during the dispute and that ops reviews within 24 hours, which is real context beyond the annotations, but it omits what state the delivery enters, whether the hold blocks payouts or cancellation, and what happens if the review rejects the claim.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two clauses, zero waste, and easy to scan, but it is terse to the point of under-specification — the brevity comes from omitted information rather than from disciplined editing.

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?

There is no output schema and the annotations are generic, so the description should carry more of the load for a mutation tool. It supplies the important funds-held/review-window behavior but leaves parameter meaning and post-review outcomes unexplained.

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 coverage is 0% and the description adds nothing about delivery_id, reason, or the evidence array (URI format, minimum length of reason). With three undocumented parameters, the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states the action; it only conveys consequences ('Funds stay held; ops reviews within 24h'). The verb+resource comes entirely from the name and title ('Open a dispute'), so the sentence adds surrounding context but not a purpose statement.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite conditions, and no mention of alternatives such as cancel_delivery or get_delivery_events that an agent might confuse with filing a dispute. The reader must infer all triggering conditions.

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.