Skip to main content
Glama

fiscal

by br.com.brasilnfe
OverviewDiscussionsAdmin

Emitir NF-EnerCom

nfenercom_emitir
Destructive

Envia a NF-EnerCom (Nota Fiscal de Energia Comercializada) para autorização na SEFAZ.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serieNoSérie da nota fiscal. Quando não informado é controlado pelo Painel
numeroNoNúmero da nota fiscal. Quando não informado é controlado pelo Painel
energiaNoInformações referente a nota de Energia
produtosYesItens da nota (mínimo 1). Cada item exige codigo, descricao, unidadeMedida, quantidade, valor, CFOP.
situacaoNoSituação do documento (Padrão 4) Valores: 1 - documento fiscal cancelado dentro do mesmo período de apuração;; 2 - documento fiscal emitido em substituição a um documento fiscal cancelado dentro do mesmo período de apuração; 3 - documento fiscal complementar; 4 - demais casos
comunicaoNoInformações referente a nota de comunicação e Telecomunicação
dataEmissaoYesData de emissão do documento. Obrigatória.
destinatarioYesInformações do destinatário (cliente). OBRIGATÓRIO.
tipoAmbienteYesTipo de ambiente. Valores: 1 - Produção; 2 - Homologação
modeloDocumentoYesModelo do documento. Valores: 6 - Energia elétrica; 21 - Comunicação; 22 - Telecomunicação
valorTotalFaturaYesValor total da fatura comercial. Deve ser > 0.
identificadorInternoNoCódigo de controle interno unico da venda. Evita duplicidades, caso configurado.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errosNoLista de erros quando a operação falha. Vazia em caso de sucesso. Cada item traz codigo, descricao e correcao.
avisosNoAvisos não bloqueantes. Pode vir preenchida mesmo em sucesso.
statusNoStatus do resultado da operação: 1 = sucesso; 2 = erro (a lista erros é preenchida).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed51 schema fields changed
    • changedInput schema / properties / comunicao / properties / tipoAssinante / enum
      Previous value: -[
-  1,
-  2,
-  3,
-  4,
-  5,
-  6
-]New value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  null
+]
    • changedInput schema / properties / comunicao / properties / tipoAssinante / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedInput schema / properties / comunicao / properties / tipoUtilizacao / enum
      Previous value: -[
-  1,
-  2,
-  3,
-  4,
-  5,
-  6
-]New value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  null
+]
    • changedInput schema / properties / comunicao / properties / tipoUtilizacao / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedInput schema / properties / comunicao / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • removedInput schema / properties / dataEmissao / format
      Removed value: -"date-time"
    • changedInput schema / properties / destinatario / properties / codigo / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / contato / properties / email / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / contato / properties / fax / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / contato / properties / telefone / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / contato / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / cpfCnpj / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / bairro / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / cep / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / codMunicipio / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / complemento / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / logradouro / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / municipio / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / numero / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / pais / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / properties / uf / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / endereco / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / ie / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / destinatario / properties / razaoSocial / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / energia / properties / classeConsumo / enum
      Previous value: -[
-  1,
-  2,
-  3,
-  4,
-  5,
-  6,
-  7,
-  8
-]New value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  7,
+  8,
+  null
+]
    • changedInput schema / properties / energia / properties / classeConsumo / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • addedInput schema / properties / energia / properties / dataLeituraAnterior / description
      Added value: +"Data/hora ISO 8601 (ex: 2026-07-22T13:45:00-03:00)"
    • removedInput schema / properties / energia / properties / dataLeituraAnterior / format
      Removed value: -"date-time"
    • changedInput schema / properties / energia / properties / dataLeituraAnterior / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / energia / properties / dataLeituraAtual / description
      Added value: +"Data/hora ISO 8601 (ex: 2026-07-22T13:45:00-03:00)"
    • removedInput schema / properties / energia / properties / dataLeituraAtual / format
      Removed value: -"date-time"
    • changedInput schema / properties / energia / properties / dataLeituraAtual / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / energia / properties / grupoTensao / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedInput schema / properties / energia / properties / subClasseConsumo / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedInput schema / properties / energia / properties / tarifaAplicada / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedInput schema / properties / energia / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / properties / identificadorInterno / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / numero / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / codClassificacao / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / codTributacao / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / codigo / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / desconto / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / descricao / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / outrasDespesas / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedInput schema / properties / produtos / items / properties / unidadeMedida / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / serie / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / avisos / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
    • changedOutput schema / properties / erros / items / properties / codigo / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / erros / items / properties / correcao / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / erros / items / properties / descricao / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / erros / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the write/external-call profile is covered. The description usefully adds that the document is submitted to SEFAZ for authorization, confirming the external authority, but says nothing about irreversibility, whether homologation is safe, or what happens after authorization.

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?

A single front-loaded sentence with no filler; the verb and destination come first. It is efficiently structured though extremely terse given the tool's complexity.

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?

For a 12-parameter, destructive, open-world emission tool, the description omits critical context: that it is an irreversible fiscal transmission, the Production vs Homologation implications, and any preconditions. An output schema exists so return values need not be explained, but the operational stakes are left undisclosed.

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% with 12 parameters, nested objects, and 3 enums, so the schema fully documents field meaning (modeloDocumento, tipoAmbiente, produtos requirements, etc.). The description adds no parameter-level guidance beyond what the schema already provides, so the baseline 3 applies.

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 (Envia/sends), a specific resource (NF-EnerCom, with the Portuguese expansion of the acronym), and the target destination (SEFAZ authorization). This separates it from peers like nfenercom_gerar_arquivo, though it never names that sibling to sharpen the distinction.

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 indication of when to use this tool versus nfenercom_gerar_arquivo, nfe_emitir, or nfe_emitir_complementar, and no prerequisites stated (e.g. that it actually transmits for authorization rather than pre-visualizing). The agent must infer usage entirely from the name.

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

All fiscal toolsInspect
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.

Resources