fiscal

Manifestar destinatário

evento_manifestar

Destructive

Registra a manifestação do destinatário sobre uma NF-e. TipoEvento: 0=ciência da operação, 1=confirmação da operação, 2=desconhecimento, 3=operação não realizada.

Input Schema

TableJSON Schema

Name	Required	Description
`Chave`	Yes	Chave de acesso de 44 dígitos da NF-e a manifestar.
`TipoAmbiente`	Yes	Ambiente do documento original (DEVE bater com o ambiente onde a nota foi emitida). IMPORTANTE: passe explicitamente. Manifestação de NF de prod precisa ser ambiente 1. Valores: 1 - Produção; 2 - Homologação
`Justificativa`	No	Justificativa. OBRIGATÓRIA quando TipoManifestacao = 4 (mínimo 15 caracteres). Para outros tipos pode omitir.
`NumeroSequencial`	No	Número sequencial do evento (1 a 20). Se omitido, o sistema usa o próximo disponível.
`TipoManifestacao`	Yes	Tipo da manifestação do destinatário. Valores: 1 - Confirmação da Operação; 2 - Ciência da Operação; 3 - Desconhecimento da Operação; 4 - Operação não Realizada (exige Justificativa com 15+ caracteres)

Output Schema

TableJSON Schema

Name	Required	Description
`Error`	No	Mensagem de erro da operação. Vazia ("") quando foi bem-sucedida.
`Avisos`	No	Avisos não bloqueantes. Pode vir preenchida mesmo em emissão bem-sucedida.
`Status`	No	1 - Evento Processado; 2 - Aguardando processamento do evento; 3 - Ocorreu um erro ao processar o evento
`DsEvento`	No
`DsMotivo`	No
`Base64Xml`	No	XML do evento processado (procEventoNFe) em Base64. Preenchido apenas quando o evento e autorizado (cStat 135) e o documento e NF-e (modelo 55). Nulo nos demais casos.
`Base64File`	No	PDF do documento auxiliar do evento (ex.: Carta de Correcao) em Base64. Preenchido apenas quando o evento e autorizado e a nota existe na base. Nulo nos demais casos.
`DsAmbiente`	No
`NuProtocolo`	No
`NumeroSequencial`	No
`CodStatusRespostaSefaz`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 8, 2026

addedOutput schema / properties / Base64File

Added value: +{
+  "description": "PDF do documento auxiliar do evento (ex.: Carta de Correcao) em Base64. Preenchido apenas quando o evento e autorizado e a nota existe na base. Nulo nos demais casos.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / Base64Xml

Added value: +{
+  "description": "XML do evento processado (procEventoNFe) em Base64. Preenchido apenas quando o evento e autorizado (cStat 135) e o documento e NF-e (modelo 55). Nulo nos demais casos.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed8 schema fields changedJul 22, 2026

changedInput schema / properties / Justificativa / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / NumeroSequencial / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

changedOutput schema / properties / Avisos / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

changedOutput schema / properties / DsAmbiente / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / DsEvento / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / DsMotivo / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / Error / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / NuProtocolo / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

First observedJul 1, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing behavioral – it omits that this transmits an irreversible fiscal event to SEFAZ, that repeated manifestations are limited, or any timing constraint, which matters greatly for a destructive, open-world write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences and front-loaded with the core action, which is good. But the second sentence is not merely redundant – it is incorrect relative to the schema, so it does not earn its place.

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

Completeness2/5

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

An output schema exists, so return values need no explanation. Still, for a destructive fiscal mutation with three required parameters and a legal-deadline semantics, the description omits environment-matching rationale, irreversibility, and correct enum documentation – the essentials for calling it correctly.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description actively misleads: it references "TipoEvento" with values 0=ciência, 1=confirmação, 2=desconhecimento, 3=não realizada, while the actual schema parameter is "TipoManifestacao" with a different numbering (1=Confirmação, 2=Ciência, 3=Desconhecimento, 4=Não Realizada). An agent following the description could send a wrong enum value.

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?

States a specific verb and resource ("Registra a manifestação do destinatário sobre uma NF-e"), so an agent knows the core action. However, it then describes a parameter named "TipoEvento" with values 0-3 that does not exist in the schema, which muddies rather than sharpens the stated purpose.

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

Usage Guidelines2/5

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

No guidance on when to manifest versus using siblings such as evento_cancelar or evento_carta_correcao, nor any mention of the legal deadline or prerequisites (e.g., the NF-e must exist and the environment must match). The agent must infer usage entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fiscal tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.