Lista notas fiscais (NF-e) emitidas (ListarNF). Paginado. filters (JSON) aceita dEmiInicial/dEmiFinal (DD/MM/AAAA), filtrar_por_status (N=vigente, C=cancelada), tpNF (0=entrada,1=saída) etc.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| account | No | ||
| filters | No | ||
| page_size | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, and not destructive. The description adds that the tool is paginated and specifies filter structure, providing valuable behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the purpose, and provides key filter details without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description lacks information about return values. It covers main purpose and filter options but omits details on pagination parameters and output format, making it adequate but not fully comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema coverage, the description partially compensates by detailing the filters JSON parameter (date range, status, type). However, it does not explain page, account, or page_size parameters, missing an opportunity to add full semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists issued fiscal notes (NF-e) in Portuguese, with pagination and filter details, making the purpose unambiguous and distinct from sibling tools that list other resources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives like omie_list_receivables or omie_list_payables. However, the tool name and description imply it is for invoices, and sibling tools cover different resources.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The core Omie operations are distinct by resource and action, and the descriptions actively call out edge cases like omie_lancar vs omie_create_payable/receivable and transfer vs manual entries. A few pairs (list_payables/list_receivables/list_financial_movements/list_checking_account_entries) still overlap enough that an agent could pick the wrong one on first attempt.
The dominant pattern is clear and consistent: omie_verb_noun with create, get, list, update, delete, settle, cancel, and reconcile. The main deviations are the Portuguese helper omie_lancar and the unprefixed platform-level tools like authenticate, connect, marketplace, and toolkit_info, which break the otherwise regular naming scheme.
With 50 tools, this server is far beyond the 3-15 well-scoped range and sits at the extreme end of the rubric. Most of the tools are individually purposeful, but exposing checkings, payables, receivables, reconciliation, attachments, invoicing, batch upserts, and an entire marketplace platform in one server heavily taxes an agent's tool-selection space.
The core financial lifecycle is well covered: create, read, update, delete, settle, cancel, reconcile, unreconcile, transfer, attachment upload, and batch upsert. Minor gaps exist—invoices are list-only, customers have no delete operation, and there is no dedicated get-by-id for checking accounts—but these are workable for the main reconciliation workflows.