fiscal

Manifestar destinatário

evento_manifestar

Destructive

Registra a manifestação do destinatário sobre uma NF-e. TipoManifestacao: 1=confirmação da operação, 2=ciência da operação, 3=desconhecimento, 4=operação não realizada (exige Justificativa com 15+ caracteres).

Input 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

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

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this writes an external, non-trivial event. The description's type/Justificativa rules are behavioural additions, but it never says the event is registered with SEFAZ irreversibly, cannot be retracted, or what error states to expect.

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?

Two compact sentences with the action front-loaded and the enum semantics immediately after. Minor redundancy with the schema's TipoManifestacao description, but 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?

With a full output schema and complete parameter documentation, the description only needs to frame the operation, which it does. The missing piece is operative context (irreversibility, environment matching risk already noted in schema), not call-shaping detail.

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 TipoManifestacao, Chave, TipoAmbiente and Justificativa are already fully documented in the schema. The description only restates the TipoManifestacao enum, adding no syntax or format detail beyond structured data — baseline 3.

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") and enumerates the four manifestation types, so the agent knows exactly what the call does. It does not explicitly contrast itself with nearby event siblings such as evento_cancelar or cte_desacordo, which keeps it below a 5.

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

Usage Guidelines3/5

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

The description gives one concrete usage rule — type 4 requires a Justificativa of 15+ characters — which steers invocation. It offers no guidance on when to choose this event over other event tools, nor preconditions such as the NF-e needing to be addressed to the CNPJ.

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.