Skip to main content
Glama

Report a problem with an order

report_issue
Destructive

Open a support case for an order (damaged / missing / wrong item, stain not removed, late delivery, re-clean, other). Works with the connected Fold account, or with order code + the email used when scheduling. A Fold specialist follows up by text or email; re-cleans are free. Describe what happened in the customer's words.

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": {
      "orderCode": "<orderCode>",
      "issueType": "<issueType>",
      "description": "<description>"
    },
    "name": "report_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail used when scheduling. Not needed with a connected account.
issueTypeYes
orderCodeYes
descriptionYes10–2000 characters.
preferredResolutionNoOptional, e.g. "re-clean" or "refund for the shirt".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Email used at booking. Not needed with a connected account."New value: +"Email used when scheduling. Not needed with a connected account."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description adds useful context beyond the annotations: it explains the connected-account alternative, the email requirement when no account is connected, the specialist follow-up, and that re-cleans are free. It does not explain the annotation's destructiveHint=true or describe what side effect opening the support case may have.

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?

The description is front-loaded with the core action and then provides only relevant operational context. Four sentences cover purpose, authentication path, follow-up expectations, and description guidance without repetition or filler.

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?

The description is largely complete for invoking the tool: it covers the required order code, issue type, and description content, plus account-vs-email authentication and follow-up expectations. The main gap is that it does not clarify the destructive behavior declared by the annotations or mention the optional preferredResolution parameter.

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?

With 60% schema description coverage, the description adds some meaning by listing issue categories and telling the agent to capture the customer's own words. It still omits guidance for preferredResolution and does not add orderCode format details, while the email and description-length semantics are already largely covered in the schema.

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: "Open a support case for an order," and lists the problem categories it covers. This clearly separates it from order-management siblings such as cancel_order or reschedule_order, although it does not explicitly name 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 the tool by enumerating issue types such as damaged, missing, late delivery, and re-clean. However, it does not explicitly state when not to use it or contrast it with related sibling tools like cancel_order or reschedule_order.

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