Skip to main content
Glama

dispute_delivery

DestructiveIdempotent

Buyer records a delivery dispute. Trial limitation: credits stay reserved and no adjudication/resolution is currently available. This does not refund credits.

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": {
      "order_id": "<order_id>"
    },
    "name": "dispute_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason for dispute
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, so the mutation profile is known. The description adds genuinely useful context beyond that: credits stay reserved, no resolution occurs, and no refund is issued — exactly the kind of consequence an agent needs before calling a destructive tool.

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, front-loaded with the action, followed by the two consequences that matter most. No filler and no restatement of the tool name.

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, the description covers the critical unknowns: what happens to credits and that no adjudication occurs. It does not say what is returned (e.g., a dispute identifier), which is the only meaningful gap.

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-schema and order_id is self-evident from its name and constraints. The description adds no parameter-level meaning (no format hints, no guidance on what makes a valid order_id or a good reason), so it neither compensates for nor worsens the gap; baseline 3 applies.

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 — 'Buyer records a delivery dispute' — naming both the actor and the action, which clearly separates it from siblings like accept_delivery or deliver_order. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated in-text.

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?

Usage is implied: a buyer invokes this when they want to contest a delivery rather than accept it. The trial limitation ('no adjudication/resolution is currently available') functions as a partial when-not signal, but there is no explicit statement of prerequisites or named alternatives.

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