Skip to main content
Glama

Cotar frete

quote_shipping
Read-only

Cota o frete (Correios e retirada na loja) para um CEP e uma lista de produtos com quantidades, sem precisar de carrinho. Devolve as opções com id, nome, valor em reais e prazo em dias úteis após o pagamento, e a regra de frete grátis do estado, quando houver.

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": {
      "cep": "<cep>",
      "produtos": "<produtos>"
    },
    "name": "quote_shipping"
  }
}

Input Schema

NameRequiredDescriptionDefault
cepYesCEP de entrega, com ou sem traço (ex.: 12223-830).
produtosYesProdutos a enviar: [{"codigo": "M10469", "quantidade": 2}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the return shape (id, nome, valor em reais, prazo em dias úteis após o pagamento) and the free-shipping rule per state — important since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that names the operation, the scope constraint, the inputs and the outputs in that order. No redundant or filler wording.

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 only two fully documented parameters and annotations covering safety, the description's main obligation is the return contract, which it fulfills since no output schema exists. Minor gaps remain around failure modes (invalid CEP, unavailable product) and how the free-shipping rule interacts with the returned options.

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 both parameters are already documented in the schema, including the CEP format example and the product-list example. The description only restates that inputs are a CEP and a product list with quantities, adding no format or edge-case detail beyond the schema.

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?

States a specific verb (cota) and resource (frete) plus the two supported modalities (Correios e retirada na loja) and the exact inputs (CEP + product list with quantities). The clause 'sem precisar de carrinho' separates it cleanly from the cart-based siblings like add_to_cart, get_cart and set_shipping_method.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes the usage context explicit: quote shipping before/without building a cart, using a CEP and product list. It does not name a direct alternative or state when-not to use it (e.g., versus set_shipping_method during checkout), so it stops short of full routing guidance.

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