Skip to main content
Glama

Buscar pedido

buscar_pedido
Read-only

Fetch order and buyer details as registered at purchase, including masked CPF and contact data, to compare chargeback evidence against Clause 8.10.C; card data excluded.

Instructions

Dados do pedido e do comprador COMO CADASTRADOS NA COMPRA (nome, endereço, CPF mascarado, e-mail, tipo físico/digital, data, valor). É contra esses dados que as provas são comparadas (Cláusula 8.10.C). Não inclui dados do cartão.

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": {
      "contestacao_id": "<contestacao_id>"
    },
    "name": "buscar_pedido"
  }
}

Input Schema

NameRequiredDescriptionDefault
contestacao_idYesID da contestação, ex.: CB-002

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, so the bar is lower, and the description still adds real value: it discloses the exact returned field set, that CPF is masked, and — importantly for an agent's expectations — that card data is deliberately absent, preventing a fruitless search. It says nothing about behavior when the contestação is not found or the order is missing, which keeps it at 4.

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 tight sentences, front-loaded with the data scope, then the comparative purpose, then the exclusion. No filler; the uppercase emphasis is slightly noisy but the ordering is deliberate and efficient.

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?

With one parameter, no output schema, and read-only annotations, the description carries the return-value burden and does so by enumerating the fields the agent will receive. The only meaningful gap is the absence of any not-found or failure expectation for a lookup keyed on a contestação ID.

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% with a single parameter (contestacao_id) that is fully documented with pattern and example in the schema itself. The description adds no meaning about the parameter, so the baseline 3 applies.

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 clearly identifies the resource: order and buyer data exactly as registered at purchase, with a concrete field list (name, address, masked CPF, email, physical/digital type, date, amount). The fetch verb is only implied by the name/title rather than stated, which keeps this just short of a 5, but the scope is unambiguous and it explicitly excludes card data, distinguishing it from sibling lookups.

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 mention that evidence is compared against this data (Clause 8.10.C) signals the tool belongs to a contestation-verification workflow, and 'Não inclui dados do cartão' hints that card data must come from elsewhere. However, no sibling is named and no explicit when-to-use / when-not-to-use rule is given, so the agent must infer the routing.

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