Gera o relatório contábil/gerencial (GerarRelatorio). Período por data_inicio/data_fim (ISO AAAA-MM-DD). Pode devolver um id de relatório, baixe com f360_baixar_relatorio.
| Name | Required | Description | Default |
|---|---|---|---|
| contas | No | ||
| account | No | ||
| data_fim | Yes | ||
| data_inicio | Yes | ||
| cnpj_empresas | No | ||
| modelo_contabil | No | ||
| modelo_relatorio | 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 declare readOnlyHint=true and idempotentHint=true. Description adds that it returns an id and should be used with download sibling, but does not discuss potential side effects, rate limits, or error handling.
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?
Two sentences, directly to the point, no unnecessary words. Front-loaded with core purpose.
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?
Provides essential flow (generate then download) but lacks explanation of non-obvious parameters and return value details. For a 7-param tool, more context on filters is expected.
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?
Only describes data_inicio and data_fim with format, leaving 5 other parameters (contas, account, cnpj_empresas, modelo_contabil, modelo_relatorio) unexplained. With low schema description coverage (0%), the description fails to compensate adequately.
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?
Description clearly states it generates accounting/management reports and specifies period via dates. It differentiates from the sibling f360_baixar_relatorio by noting the output is an id for download.
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?
Provides indirect guidance by mentioning that the report id can be downloaded with f360_baixar_relatorio, but no explicit when-to-use vs alternative report tools (e.g., f360_relatorio_conciliacao_cartoes).
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.
Most tools are clearly distinct, especially the f360_* family which separates listing, detail, and report generation per resource. However, 'authenticate' and 'connect' both deal with connection state, and 'f360_list_accounts' vs 'f360_listar_planos_contas' could be confused without reading descriptions closely.
Naming is inconsistent: generic tools use simple English verbs (connect, show_version), while financial tools mix English (list_accounts) and Portuguese (listar_notas, obter_xml) with inconsistent verb forms and prefixes. The patterns are not predictable across the full set.
At 19 tools, the set is borderline heavy. Six tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are platform-level utilities unrelated to the financial domain, inflating the count; the remaining 13 financial tools are well-scoped for a read-only reporting API.
The financial tools cover listing and detail retrieval for core entities (accounts, notes, people, chart of accounts) and generate/download reports. However, there are no create/update/delete operations, and no getter for accounts or other entities, limiting the surface to read-only reporting.