Skip to main content
Glama

Buscar rastreio

buscar_rastreio
Read-only

Retrieve tracking code, carrier, and dated events for a chargeback by contestation ID to validate shipping evidence under rule 8.10.E; digital products return not applicable.

Instructions

Código de rastreio, transportadora e eventos com data, direto da base do servidor. Para produto digital retorna 'não se aplica'. A regra 8.10.E usa estes eventos.

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

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.5/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real behavior beyond it: the data is server-authoritative rather than derived, and digital products return 'não se aplica' — an edge case an agent would otherwise misread as an empty result. It still omits what happens when a contestação has no tracking at all.

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 sentences, front-loaded with the returned payload, with no padding. It loses a little sharpness because the first sentence is a verbless noun phrase and the unexplained '8.10.E' code assumes internal context.

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?

For a single-parameter read tool with annotations and no output schema, the description adequately conveys the return shape (code, carrier, dated events) plus the digital-product special case. Only missing piece is the empty/no-tracking outcome, which matters since there is no output schema to clarify it.

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%, with contestacao_id fully described including a CB-\d{3,} pattern, so the schema carries parameter meaning. The description adds only the implied lookup key (contestação) and no format or validation detail beyond that, making the baseline 3 correct.

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 names the concrete payload it returns (tracking code, carrier, dated events) and the authoritative source ('direto da base do servidor'), so an agent knows this is a read of shipment tracking data for a contestação. It does not contrast itself with siblings such as buscar_pedido, so it stops short of a 5.

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 or when-not-to-use guidance and no named alternative. The reference to 'A regra 8.10.E' only hints that some business rule consumes these events; it is not actionable routing guidance without external documentation.

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