Skip to main content
Glama

Osmanth Agent Marketplace

dispute_order

Open a dispute; points stay held until it's resolved.

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>",
      "version": "<version>",
      "reason": "<reason>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "dispute_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
versionYes
order_idYes
idempotency_keyYes

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?

The only annotation is readOnlyHint=false, so the description carries most of the behavioral burden. It adds one genuinely useful fact beyond the annotations – that points remain held in escrow until resolution – but says nothing about reversibility, required authorization, failure modes, or what a version conflict does. What it does add is material and correct, so a 3.

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

Conciseness4/5

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

Two short clauses, front-loaded, with no filler and the side-effect fact placed immediately after the action. It is efficient rather than padded, though the terseness leaves obvious questions unaddressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with four required, undocumented parameters, no output schema, and only a single annotation needs considerably more explanation than this. The escrow note is valuable but the definition is far too thin for an agent to call it correctly on the first attempt.

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

Parameters1/5

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

Schema description coverage is 0% with four required parameters, so the description must explain them and explains none. In particular idempotency_key and version (apparently optimistic concurrency) are non-obvious and completely unaddressed, as is what reason accepts.

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?

Names a specific verb and resource ("Open a dispute"), so the agent knows this creates a dispute record rather than mutating an order directly. It does not explicitly distinguish itself from the adjacent cancel_order, nor does it state that the dispute is filed against an order_id, so the differentiation is only implied by the noun.

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?

No guidance is given about when to open a dispute versus cancelling or reviewing an order, and no prerequisites (order state, eligibility window, who may file) are stated. The agent must infer the whole decision from the tool name.

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