Skip to main content
Glama

Situação do pedido

get_order_status
Read-only

Situação de um pedido feito nesta sessão: aguardando pagamento, pago, enviado (com código de rastreio), entregue ou cancelado, com o link do pedido.

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": {
      "session_token": "<session_token>",
      "pedido_id": "<pedido_id>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pedido_idYesNúmero do pedido (de place_order).
session_tokenYesO session_token devolvido por start_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds useful behavioral detail: the exact status vocabulary, that 'enviado' includes a tracking code, and that the order link is returned. It does not discuss failure behavior for invalid or expired session tokens, which is the main remaining gap.

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 front-loaded sentence: resource first, then the enumerated status values, then the returned link. The status enumeration is long but each item conveys distinct information an agent would otherwise have to guess.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so by listing statuses, the tracking code, and the order link. Combined with full schema coverage and clear read-only annotations, an agent has enough to call this correctly.

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 description coverage is 100% and the schema already explains both parameters, including that pedido_id comes from place_order and session_token from start_session. The description adds only the session-scoping nuance ('nesta sessão'), so the baseline of 3 is appropriate.

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+resource (retrieve the status of an order) and enumerates the possible outcomes (aguardando pagamento, pago, enviado, entregue, cancelado), which lets an agent understand what it will get back. It also scopes the tool to orders 'feito nesta sessão', separating it from general order lookup, though it does not name a sibling alternative.

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 phrase 'pedido feito nesta sessão' plus the schema note that pedido_id comes from place_order signals this is a post-purchase status check. There is no explicit when-to-use/when-not or comparison against siblings such as get_cart or get_checkout_link.

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