Skip to main content
Glama

Open a return

start_return

USE THIS when the human wants to send something back. Opens a return and returns the exact next steps, who pays the return shipping, and which evidence to record. Do not promise a refund yourself; this tool sets the terms.

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>"
    },
    "name": "start_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
reasonYeschanged_mind | wrong_item | defective | damaged | missing_parts
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare that this is not read-only, not destructive, and closed-world; the description adds real behavioral context by saying it returns next steps, who pays return shipping, and which evidence to record, and that it establishes the terms so the agent shouldn't promise refunds. It does not say whether calling twice creates duplicate returns or what authorization/order state is required.

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?

Three short sentences, with the triggering condition placed first and no filler. The final clause about 'sets the terms' partially restates the refund caution, a minor redundancy.

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?

With no output schema, the description usefully tells the agent what comes back (next steps, shipping payer, evidence) and warns against over-promising refunds, which is adequate for a 3-parameter mutation. The gap is parameter-level detail for order_id and note.

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 only 33%: reason is enumerated in the schema, but order_id and the optional note are undocumented anywhere. The description never mentions any parameter, so it fails to compensate for the low coverage.

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

Purpose5/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 return') plus the trigger situation ('when the human wants to send something back'), which cleanly separates it from siblings like cancel_order or create_order. An agent can decide to call this without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit, front-loaded invocation condition ('USE THIS when the human wants to send something back') and a guardrail ('Do not promise a refund yourself'). It stops short of naming an alternative or an explicit when-not case, so it is strong but not complete routing guidance.

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