Gera o relatório de transferências entre contas (GerarRelatorioTransferenciasEntreContas) por período. Pode devolver um id, baixe com f360_baixar_relatorio.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| data_fim | Yes | ||
| data_inicio | Yes | ||
| cnpj_empresas | 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 read-only and idempotent behavior. The description adds value by stating that the tool may return an id, implying an asynchronous or deferred download pattern. No contradictions with 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 extremely concise with two sentences. The first sentence immediately states the purpose and scope, and the second covers the return behavior and next steps. No 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 the tool has 4 parameters, no output schema, and moderate complexity, the description covers the core function and return behavior. However, it lacks details on parameter formats, required vs optional fields, and the structure of the report. Additional context would be needed for robust use.
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 description coverage, the description should explain all parameters. It only briefly implies that data_inicio and data_fim define the period, but does not clarify account or cnpj_empresas. Two of four parameters are left completely unexplained.
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 the tool generates a report of transfers between accounts by period, using a specific verb and resource. It also distinguishes from the sibling tool f360_baixar_relatorio by mentioning the return of an id.
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 provides partial guidance by noting that an id can be returned and should be used with f360_baixar_relatorio. However, it does not differentiate this tool from other report generation tools (e.g., f360_relatorio_conciliacao_cartoes), leaving the agent to infer when to use this specific one.
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.