Skip to main content
Glama

Confirmar e emitir a NFS-e

confirmar_emissao
Destructive

Emite DE VERDADE a nota da prévia. Chame apenas depois que o usuário aprovou a prévia nesta conversa. Idempotente: o mesmo token nunca emite duas vezes. Autorizada, devolve danfse_url (PDF) e xml_url — links para o usuário abrir, que você não consegue baixar.

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": {
      "confirmacao_token": "<confirmacao_token>"
    },
    "name": "confirmar_emissao"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmacao_tokenYesToken devolvido por emitir_nota.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior1/5

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

The description claims "Idempotente: o mesmo token nunca emite duas vezes", but the annotations declare idempotentHint=false, directly contradicting the retry-safety claim an agent would act on. This matters because the tool is destructiveHint=true, so a wrong assumption about retries can cause a duplicate real invoice; the otherwise useful details about returned links do not offset the conflict.

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?

Four short sentences, front-loaded with the destructive nature of the action, then the precondition, then the safety property, then the return value. Nothing is padding.

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 destructive, no-output-schema tool this covers the essentials: when to call, what is produced (danfse_url PDF and xml_url), and the agent's inability to download those links. It omits failure modes and what happens to the prévia after a failed authorization, and the idempotency claim needs reconciling with the annotations.

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% and already documents that confirmacao_token comes from emitir_nota, so the baseline applies. The description still adds meaning by explaining that the token is single-use, which tells the agent the token cannot be recycled across approvals.

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 ("Emite DE VERDADE a nota da prévia") and contrasts it with the preview step, which is the work done by the sibling emitir_nota. The emphasis on "DE VERDADE" makes the final-emission semantics unmistakable.

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 an explicit gating condition: only call after the user approved the prévia in this conversation. It does not name emitir_nota or cancelar_nota by name, so the routing to the alternative is implied by context rather than stated.

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