Skip to main content
Glama

get_order

Read-onlyIdempotent

Retrieve order details by order ID, including status, date, customer, items, and total value, to answer order-specific questions from store data.

Instructions

Detalhes de um pedido pelo número: status, data, cliente, itens e valor total.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered and the description's burden is lower. The description adds nothing behavioral beyond that — no statement about what happens when the order number does not exist or whether any access scoping applies.

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?

One short sentence, front-loaded with the action and key, with zero filler. The trailing field list (status, date, customer, items, total) is arguably redundant given an output schema exists, which slightly dilutes rather than helps.

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?

With annotations covering safety and an output schema covering the return shape, the definition is functionally callable. However, the words spent re-listing return fields would have been better used on the one genuinely missing piece: behavior when the order number is not found.

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 'order_id' integer has no description in the schema, so the description must compensate. It partially does by clarifying that the key is the order number ('pelo número'), but it gives no format, range or validity constraints.

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 states a specific verb-and-resource pair ('Detalhes de um pedido') and narrows retrieval to lookup 'pelo número', so the agent knows this fetches one order rather than a list. It does not differentiate itself from siblings such as customer_orders, which also returns order data.

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 only implied: the phrase 'pelo número' signals that this is a single-record lookup keyed by an order number, which is enough to guess when to call it. There is no explicit when-not guidance and no mention of alternatives like customer_orders or run_sql for broader queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.