Encontra COMPRAS PARCELADAS no período (use isto, não busca por texto). Combina parcelas estruturadas e heurística para Open Finance (apresentadas como "possível parcelamento"). Sem datas, últimos 12 meses. Pode filtrar por conta/cartão.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| end_date | No | ||
| start_date | No | ||
| min_occurrences | 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. The description adds valuable behavioral context: it combines structured installments with heuristic detection for Open Finance and labels results as 'possível parcelamento'. This informs the agent that results may include uncertain classifications, which is useful beyond the 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 compact and front-loaded, with the core purpose in the first sentence and each additional sentence adding distinct information: heuristic behavior, default date range, and filter capability. There is no filler or redundancy.
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?
For a read-only discovery tool, the description covers the essential operational context: what it finds, how the heuristic works, default time range, and filtering options. The main gaps are the lack of any output schema or return-format description and the unexplained 'min_occurrences' parameter, but these are not fatal given the tool's simplicity.
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 must compensate for the four undocumented parameters. It provides some relevant context: date parameters are optional and default to the last 12 months, and the 'account' parameter appears to support filtering by account/card. However, 'min_occurrences' is not explained at all, leaving a clear gap in parameter understanding.
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 identifies the tool's purpose: finding installment purchases ('Encontra COMPRAS PARCELADAS') in a period, and explicitly distinguishes it from text search ('use isto, não busca por texto'). This makes it easy for an agent to differentiate from sibling tools like search_transactions.
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 gives explicit guidance to use this tool instead of text search and clarifies the default behavior when no dates are provided ('Sem datas, últimos 12 meses'). It also mentions optional filtering by account/card. However, it does not name specific sibling alternatives or state when NOT to use this tool beyond the text-search exclusion.
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 target distinct resource+action pairs, but the reporting/query side is crowded: get_balances, transactions_list_results, get_financial_summary, get_monthly_overview, and the category/tag reports overlap heavily. Long descriptions disambiguate bases and use cases, but an agent must read carefully to avoid picking the wrong report or list variant.
Organizze tools overwhelmingly follow a consistent organizze_<verb>_<noun> snake_case pattern with create_, list_, get_, update_, and delete_ prefixes. Deviations like transactions_list_results, the mass_* versus update_transactions_* bulk variants, and unprefixed platform tools keep it from being perfect.
68 tools is far beyond the practical agent surface and includes many near-variant list/report/mass tools plus six unrelated platform-level tools. Even though the finance domain is broad, this count creates an extreme mismatch for efficient tool selection.
The core finance lifecycle is well covered: accounts, cards, categories, budgets, transactions, invoices, transfers, and reports all have substantial CRUD or equivalent support. However, some referenced operations are missing entirely, such as delete_recurrence, clear_latest_imports, and remove_from_latest_imports, and transfers/recurrences lack full lifecycle coverage.