Skip to main content
Glama

Moqway

Get order

get_order
Read-onlyIdempotent

Order status, timeline, deadlines, shipment tracking, dispute and the actions available now.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds meaningful context about what is returned (timeline, deadlines, shipment tracking, open dispute, available next actions), which goes beyond the annotations. It does not address behavior when the order is not found or what an empty field means, so it stays at an adequate level.

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 compact sentence with no filler, and the most useful content categories lead. The fragment style is terse but nothing is padding; it could still front-load the retrieval action rather than a bare list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining the return surface, and its list of status, timeline, deadlines, shipment tracking, dispute, and available actions does that reasonably. However, for a tool that also surfaces 'actions available now,' it never says whether those actions are executed here or via siblings, leaving ambiguity about scope.

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% and the single required parameter order_id is never mentioned in the description. The agent gets the identifier's constraints (3-40 chars) only from the schema, with no hint about what form an order ID takes or where to obtain it, so the description does not compensate for the coverage gap.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase inventory ('Order status, timeline, deadlines, shipment tracking, dispute and the actions available now') rather than a verb stating retrieval, so the 'get' semantics come entirely from the name and title. It does convey the resource and contents, which helps separate it from siblings like get_order_documents or list_orders, but no sibling is named and the scoping of the lookup is unstated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of prerequisites, and no pointing to alternatives such as cancel_order, open_dispute, or get_order_documents for related needs. Usage is only implied by the list of content categories.

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