Skip to main content
Glama

Get one of my orders

get_my_order
Read-onlyIdempotent

Details of one of your own orders by number: lines with prices (null when priced on request), shipping, payment, timeline and document paths. Someone else's number returns not found. Free text is wrapped as data.

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": {
      "number": "<number>"
    },
    "name": "get_my_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesYour order number (from my_orders).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description earns credit by adding non-obvious behavior on top of that: ownership enforcement ('someone else's number returns not found'), a null-value rule for prices on request, and the note that free text is wrapped as data. It stops short of describing pagination, size limits or caching, which keeps it from a 5.

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 clauses, front-loaded with the verb and payload, followed by the error and injection notes in descending priority. The telegraphic style ('Free text is wrapped as data') is dense but every sentence carries distinct information; only the parenthetical price remark feels slightly compressed.

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

Completeness5/5

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

This is a single-parameter read with no output schema and rich annotations, and the description compensates for the missing return schema by enumerating the fields an agent will receive. Ownership failure behavior and null semantics are both disclosed, so an agent can call it and interpret the result without further information.

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 100% and the single parameter already carries its own description with a pattern constraint, so the schema does the heavy lifting. The description reinforces ownership and the provenance of the number ('from my_orders') but adds no format or syntax detail beyond the schema, which is the expected baseline here.

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?

The description opens with a specific verb and resource ('Details of one of your own orders by number') and enumerates the payload sections (lines, shipping, payment, timeline, documents). The scope qualifier 'your own' separates it from generic order lookups, and the payload listing separates it from my_orders, which supplies the number in the first place.

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?

Usage is implied rather than stated: the schema note 'Your order number (from my_orders)' and the mention that another party's number returns not found tell an agent what input to supply and what failure means. However, there is no explicit instruction about when to call this instead of track_my_order or my_order_documents, so the agent must infer the boundary.

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