Skip to main content
Glama

Moqway

Get order documents

get_order_documents
Read-onlyIdempotent

Signed download links (valid 1 hour) for the commercial invoice and packing list, available after the supplier accepts. Needed for import customs clearance.

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

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: link expiry of 1 hour and the availability gate tied to supplier acceptance. It does not say what happens if the order has not been accepted (error vs. empty result) or whether re-calling refreshes the links.

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 with zero filler, and the highest-value facts (what is returned, link lifetime) are front-loaded ahead of the precondition. Nothing is wasted; the customs-clearance note is the only mildly expendable element.

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?

For a one-parameter read tool with full annotation coverage and no output schema, the description supplies what matters: what the links are, how long they live, and when they are obtainable. Only failure-mode behavior for a not-yet-accepted order is left unspecified.

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?

Schema coverage is 0% and the single parameter order_id has no description in either place, so the description carries no additional parameter meaning. The parameter is self-evident from its name and the tool context, so the gap is small but real.

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 concrete resources returned — commercial invoice and packing list — as signed download links, which is specific and distinguishable from get_order. It never states an explicit verb like 'retrieve', but the return-value framing makes the operation unambiguous.

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 gives a clear precondition ('available after the supplier accepts') and the motivating scenario ('needed for import customs clearance'), which tells the agent when the tool is applicable. It stops short of naming an alternative or stating when not to call it.

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