Skip to main content
Glama
nikolasdehor

mcp-fiscal-brasil

by nikolasdehor

consultar_nfse

Get guidance to consult NFSe data by providing invoice number, city, and state, directing to the appropriate municipal portal.

Instructions

Consulta dados de uma NFSe (Nota Fiscal de Serviço Eletrônica). ATENÇÃO: NFSe não possui padrão nacional - cada município tem seu próprio sistema. Esta ferramenta orienta sobre como acessar o portal correto do município.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ufYesSigla do estado com 2 letras (ex.: "SP", "MG").
numeroYesNumero da NFS-e.
municipioYesNome do municipio emissor (ex.: "Sao Paulo", "Belo Horizonte").
cnpj_prestadorNoCNPJ do prestador de servico. Opcional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Despite no annotations, the description discloses that the tool provides guidance on accessing the correct portal rather than directly querying a database, adding behavioral context. However, it could be more specific about what the tool actually returns.

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 sentences, front-loaded with purpose and a crucial caution. No wasted words.

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

Completeness3/5

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

For a tool with 4 parameters and an output schema, the description is brief and could explain the output format or the nature of the guidance provided. It is minimally adequate but leaves gaps.

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 coverage is 100% and parameters are well-documented in the schema. The description does not add extra meaning beyond what the schema provides.

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?

Description clearly states the tool consults NFSe data, and the context of siblings shows many other consult tools for different documents, so it distinguishes well.

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?

Description provides a caution about NFSe's lack of national standard and guidance to access the correct municipal portal, but does not explicitly state when to use this tool versus alternatives like consultar_nfe.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikolasdehor/mcp-fiscal-brasil'

If you have feedback or need assistance with the MCP directory API, please join our Discord server