fiscal

Listar notas fiscais

nota_listar

Read-onlyIdempotent

Lista NF-e/NFC-e/NFS-e emitidas ou recebidas pela empresa em um intervalo de datas. Suporta filtros por chave, número, status e tipo.

Input Schema

TableJSON Schema

Name	Required	Description
`DtFim`	No	Data final da busca
`DtInicio`	No	Data inicial da busca
`TipoAmbiente`	No	Tipo de ambiente (Padrão 1 - Produção) Valores: 1 - Produção; 2 - Homologação
`TipoParticipacao`	No	Como a empresa participa das notas de entrada (Padrão 0 - Destinatário). Somente para TipoDocumentoFiscal = 0. Valores: 0 - Destinatário (comportamento padrão); 1 - Transportadora (NF-e onde a empresa é citada como transportadora ou terceiro autorizado); 2 - Ambos
`TipoDocumentoFiscal`	No	Tipo do documento fiscal (Padrão 0 - Entrada) Valores: 0 - Entradas; 1 - Saídas
`IdentificadorInterno`	No	Busca notas que possui o código interno informado (somente saídas)

Output Schema

TableJSON Schema

Name	Required	Description
`Error`	No	Mensagem de erro da operação. Vazia ("") quando foi bem-sucedida.
`Notas`	No
`Avisos`	No	Avisos não bloqueantes. Pode vir preenchida mesmo em emissão bem-sucedida.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 21, 2026

addedInput schema / properties / TipoParticipacao

Added value: +{
+  "description": "Como a empresa participa das notas de entrada (Padrão 0 - Destinatário). Somente para TipoDocumentoFiscal = 0. Valores: 0 - Destinatário (comportamento padrão); 1 - Transportadora (NF-e onde a empresa é citada como transportadora ou terceiro autorizado); 2 - Ambos",
+  "enum": [
+    0,
+    1,
+    2
+  ],
+  "type": "integer"
+}

addedOutput schema / properties / Notas / items / properties / TipoParticipacao

Added value: +{
+  "description": "Como a empresa participa da nota de entrada (somente TipoDocumentoFiscal = 0): Valores: 0 - Destinatário; 1 - Transportadora/terceiro citado na nota",
+  "enum": [
+    0,
+    1,
+    null
+  ],
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed1 schema field changedAug 11, 2026
- addedOutput schema / properties / Notas / items / properties / Serie
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedAug 4, 2026

addedInput schema / properties / TipoAmbiente

Added value: +{
+  "default": 1,
+  "description": "Tipo de ambiente (Padrão 1 - Produção) Valores: 1 - Produção; 2 - Homologação",
+  "enum": [
+    1,
+    2
+  ],
+  "type": "integer"
+}

Changed2 schema fields changedAug 3, 2026

addedInput schema / properties / IdentificadorInterno

Added value: +{
+  "description": "Busca notas que possui o código interno informado (somente saídas)",
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedInput schema / properties / IndentificadorInterno

Removed value: -{
-  "description": "Busca notas que possui o código interno informado (somente saídas)",
-  "type": [
-    "string",
-    "null"
-  ]
-}

Changed22 schema fields changedJul 22, 2026
- removedInput schema / properties / DtFim / format
```
Removed value: -"date-time"
```
- removedInput schema / properties / DtInicio / format
```
Removed value: -"date-time"
```
- changedInput schema / properties / IndentificadorInterno / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Avisos / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / Error / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / Cfops / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / Chave / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / CnpjDestinatario / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / CnpjEmissor / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / CodLote / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / DigestValue / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / Notas / items / properties / DtEmissao / description
```
Added value: +"Data/hora ISO 8601 (ex: 2026-07-22T13:45:00-03:00)"
```
- removedOutput schema / properties / Notas / items / properties / DtEmissao / format
```
Removed value: -"date-time"
```
- addedOutput schema / properties / Notas / items / properties / DtRecebimento / description
```
Added value: +"Data/hora ISO 8601 (ex: 2026-07-22T13:45:00-03:00)"
```
- removedOutput schema / properties / Notas / items / properties / DtRecebimento / format
```
Removed value: -"date-time"
```
- changedOutput schema / properties / Notas / items / properties / IdentificadorInterno / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / IeEmissor / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / NomeDestinatario / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / NomeEmissor / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / NumeroProtocolo / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / Notas / items / properties / ValorIcms / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / Notas / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
First observedJul 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the document-type coverage and date-range scoping, which is useful, but it also advertises filters ('chave, número, status') that have no matching schema parameter, which is mildly misleading about what can actually be filtered.

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?

Two tight sentences with the primary purpose front-loaded and the supported scope right behind it. No waste.

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?

An output schema exists, so return values need not be described, and the read-only annotations carry the safety profile. The one gap is the mismatch between the advertised filters and the actual parameters, but for a simple list tool the definition is otherwise sufficient.

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% and the schema documents every parameter including enum meanings and defaults, so the baseline is 3. The description adds no syntax or format detail beyond what the schema already provides.

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 (Lista) plus the exact resources (NF-e/NFC-e/NFS-e) and scope (emitted or received within a date range). This clearly separates it from the many emit/emitir siblings, though it never names a specific alternative tool.

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?

Usage is implied by the stated scope (date-ranged listing with filters), but there is no explicit when-to-use, when-not-to-use, or pointing to a sibling for narrowing results. Adequate but leaves routing to inference.

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.