Skip to main content
Glama

Moqway

Open a dispute

open_dispute
Destructive

Opens a dispute on a shipped or delivered order; escrow is frozen until Moqway resolves it. Give a factual description and links to photos if any.

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

Input Schema

NameRequiredDescriptionDefault
reasonYes
order_idYes
descriptionYes
evidence_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is partly covered; the description adds real consequence information the annotations do not carry: escrow is frozen until Moqway resolves it. It also adds evidence-quality guidance (factual description, photo links). It does not say whether repeated calls create duplicate disputes or whether a dispute can be withdrawn, which matters given idempotentHint=false.

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?

Two sentences, zero filler, with the consequential behavior (escrow frozen) and the eligibility condition both front-loaded before the call-to-action on evidence.

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?

For a destructive, non-idempotent mutation with no output schema and 0% schema description coverage, the description leaves important things unstated: what the caller gets back (a dispute id or object), how the reason codes should be chosen, and what happens to an existing dispute. The escrow-freeze note is valuable but not sufficient for a tool of this complexity.

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 description coverage is 0%, so the description must carry the parameter burden, and it largely does not: order_id is never named, the six-value reason enum is never explained or mapped to situations, and no length or format constraints are mentioned. Only description and evidence_urls get loose treatment ("give a factual description and links to photos if any").

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 and resource ("Opens a dispute") plus an eligibility scope ("on a shipped or delivered order"), which is enough to distinguish it from siblings like cancel_order or confirm_receipt without naming them. It stops short of explicitly contrasting with those alternatives.

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 description implies when to use it via the precondition that the order must be shipped or delivered, and implicitly it is the path when something went wrong with the goods. It never states when not to use it, e.g. that an unshipped order should go through cancel_order instead, or what to do if the issue is already resolved.

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