Skip to main content
Glama

Enviar código por e-mail

request_email_code

Envia um código de 6 dígitos para o e-mail do cliente, para confirmar que é ele quem está comprando. Peça ao cliente o código que chegou no e-mail e chame verify_email_code nesta mesma sessão. O código vale 15 minutos; no máximo 3 envios por e-mail a cada 15 minutos.

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

Input Schema

NameRequiredDescriptionDefault
emailYesE-mail do cliente.
session_tokenYesO session_token devolvido por start_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, non-open-world write; the description adds real behavioral facts the annotations do not carry — 15-minute code validity and a rate limit of 3 sends per e-mail per 15 minutes, plus the session-binding requirement. It stops short of saying what the response returns or what happens when the rate limit is hit, so it is strong but not exhaustive.

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 ordered purpose → next step → operational limits, with no repetition of the title or schema fields. Every sentence carries information an agent needs.

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 2-parameter tool with no output schema, the description covers what the tool does, what the customer must do, the validity window, and the rate limit — enough to call it correctly and handle the common failure mode. Only the return value (e.g., confirmation detail) is left implicit.

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% and both parameters (email, session_token) are already documented in the schema, including that session_token comes from start_session. The description adds no new syntax or constraints beyond what the schema states, so the baseline of 3 applies.

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 ('Envia um código de 6 dígitos para o e-mail do cliente') plus the goal ('confirmar que é ele quem está comprando'), and explicitly pairs with the sibling verify_email_code, so an agent can distinguish the send step from the verify step immediately.

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?

Gives explicit sequencing: send the code, ask the customer for it, then call verify_email_code 'nesta mesma sessão'. The same-session constraint is a genuine when/how-to-use rule, and the sibling to use next is named outright.

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