Skip to main content
Glama

request_aftersale

Refund (refund_only, small amounts or quality issues) or return+refund (return_refund, books free courier pickup: each user gets 3 free pickups/month).

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_no": "<order_no>",
      "type": "<type>"
    },
    "name": "request_aftersale"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
pickupNo
reasonNo
order_noYes
user_refNo
reason_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose a useful operational fact — free courier pickup with a 3/month per-user cap — which explains the pickup parameter's business meaning. However it never states this is an irreversible mutation, what permissions/auth are needed, or what happens on success.

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?

A single dense parenthetical sentence with no filler; the primary branch (refund) is front-loaded and the alternative follows. The nested-parenthesis styling is slightly hard to parse but wastes no words.

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?

This is a 6-parameter mutation tool with 0% schema coverage, no annotations, and no output schema, so the description does the bulk of the explanatory work. It covers only the mode choice and leaves parameter meanings, side effects, and outcome unspecified — inadequate for the tool's 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% across 6 parameters, so the description should compensate. It fully explains the 'type' enum and implicitly explains 'pickup' via the free-pickup note, but says nothing about order_no, user_ref, reason, or reason_class. Two of six parameters receive any semantic treatment.

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 names the two concrete after-sale actions (refund-only vs return+refund) and ties each to a specific type value, so the resource and operation are clear. It does not explicitly say it initiates a new request for an order, but the modes are unambiguous. Siblings are unrelated commerce tools, so no differentiation is needed.

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?

It tells the agent which branch to pick: 'refund_only' for small amounts or quality issues, 'return_refund' when goods must be sent back. That is explicit selection guidance. It omits prerequisites (e.g., order must be delivered) and when not to use it at all.

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