Skip to main content
Glama

Dados do cliente

set_customer_details

Completa os dados que o pedido exige: nome completo, CPF e telefone com DDD. Só preenche o que estiver em branco na conta do cliente; um CPF diferente do cadastrado é recusado. Exige verify_email_code.

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

Input Schema

NameRequiredDescriptionDefault
cpfNoCPF (11 dígitos).
nomeNoNome completo.
telefoneNoTelefone com DDD, ex.: (12) 99158-6991.
session_tokenYesO session_token devolvido por start_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses real behavioral traits: it only fills fields that are blank on the customer account, so existing data is preserved, and a CPF differing from the registered one is rejected. The email verification prerequisite adds another operational constraint an agent must satisfy. It does not say what a successful response contains or whether the call is idempotent across retries.

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?

Three short sentences, front-loaded with the action and the required fields, then the update semantics, then the precondition. Every sentence carries distinct information with no filler.

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 non-destructive partial-update tool with full schema coverage and annotations covering the safety profile, the definition covers fields, merge behavior, validation rejection, and the prerequisite. The only gap is describing the outcome of a successful call, which no output schema supplies.

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%, so each parameter including session_token is already documented in the schema. The description restates the three data fields but adds no format, validation, or inter-parameter meaning beyond what the schema provides; 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 names a specific verb and resource ('Completa os dados que o pedido exige') and enumerates the exact fields (nome completo, CPF, telefone com DDD), so an agent knows precisely what changes. It implicitly separates itself from siblings like set_shipping_address by scoping to the customer record, though it never names an alternative tool.

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?

It gives clear context for use — the data the order requires — and states a hard prerequisite ('Exige verify_email_code'), pointing at a specific sibling that must run first. It does not spell out when-not to use it or name any alternative for overlapping data.

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