Skip to main content
Glama

Endereço de entrega

set_shipping_address

Define o endereço de entrega pelo CEP: rua, bairro, cidade e estado vêm da consulta do CEP. Informe número, complemento e o nome de quem recebe. Cota o frete e devolve o carrinho com as opções de frete (use o id em set_shipping_method).

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>",
      "cep": "<cep>"
    },
    "name": "set_shipping_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
cepYesCEP de entrega, com ou sem traço (ex.: 12223-830).
bairroNoBairro, só para CEP geral de cidade.
numeroNoNúmero (ou "s/n").
enderecoNoRua, só para CEP geral de cidade (quando a consulta do CEP não traz a rua).
complementoNo
destinatarioNoNome de quem recebe. Padrão: o nome do cliente, depois de verify_email_code.
session_tokenYesO session_token devolvido por start_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real behavior beyond that — the tool performs a CEP lookup to populate fields, triggers a shipping quote, and returns the cart with freight options. It does not mention permission/authentication needs beyond the session_token or what happens when an existing address is overwritten.

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 mechanism (address defined from CEP), then the caller's inputs, then the side effect and next step. The middle sentence slightly overlaps the schema's parameter descriptions but the ordering and density are appropriate.

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 7-parameter mutation with no output schema, the description adequately compensates by stating that it returns the cart with shipping options. Gaps remain around invalid CEP handling and whether an existing address is replaced, but nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3, but the description adds meaning by partitioning inputs: rua/bairro/cidade/estado arrive from the CEP consult, while the caller supplies número, complemento and destinatário. It still does not restate the schema's fallback rule for generic city CEPs where the street is unknown, which is left to 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 and resource ('Define o endereço de entrega'), plus the scope of how the address is built: rua/bairro/cidade/estado come from the CEP lookup rather than from the caller. It also names the downstream sibling ('use o id em set_shipping_method'), so an agent can place it in the checkout flow without opening another schema.

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?

Gives clear sequencing: call this with CEP plus número/complemento/destinatário, then pass the returned shipping option id to set_shipping_method. That is a strong next-step routing cue, but there are no explicit exclusions (e.g., when to use set_customer_details instead, or what to do if the cart is empty).

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