Skip to main content
Glama

Confirmar código do e-mail

verify_email_code

Confirma o código de 6 dígitos que o cliente recebeu no e-mail (de request_email_code nesta sessão) e liga o cliente a esta sessão por 2 horas. Depois disso dá para completar os dados (set_customer_details) e fazer o pedido (place_order). "nome" (nome completo) só preenche o nome de um cliente sem nome. Cinco códigos errados invalidam o código.

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

Input Schema

NameRequiredDescriptionDefault
nomeNoNome completo, usado se o cadastro não tiver.
codigoYesO código de 6 dígitos.
session_tokenYesO session_token devolvido por start_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's real added value is the 2-hour session linkage and the failure threshold ('Cinco códigos errados invalidam o código'), which is a real side effect not visible in annotations. It stops short of describing what happens on success return or on attempts 1-4, so it is strong but not complete.

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?

The core action is front-loaded and every clause carries information, from the flow to the failure threshold. The 'nome' caveat is inserted mid-stream between the flow sentences, which slightly interrupts the sequence, and there is a stray trailing space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by explaining the resulting state (customer linked to the session for 2 hours) and the next steps available. For a three-parameter verification tool this covers everything an agent needs to call it correctly.

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 100%, so the baseline is 3; the description earns an extra point by tying 'codigo' to its origin in request_email_code within the session and by clarifying the conditional effect of 'nome' (only fills the name when the customer has none). The remaining schema fields are otherwise restated rather than expanded.

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 object ('Confirma o código de 6 dígitos') plus the source of that code ('request_email_code nesta sessão'), which distinguishes it unambiguously from any other sibling in the checkout flow.

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

Usage Guidelines5/5

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

The description places the tool in an explicit sequence: the code must come from request_email_code in the same session, and after success the agent should call set_customer_details and place_order. The 2-hour window makes the temporal precondition clear, leaving little for the agent to infer.

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