Lista as contas fixas CADASTRADAS (lançamentos recorrentes/infinitos): aluguel, assinaturas, salário, etc., com periodicidade, valor e a próxima ocorrência. Só traz recorrências cadastradas (contas/cartões MANUAIS); em conectados (Open Finance) volta vazio — para assinaturas use find_subscriptions. NÃO inclui parcelamentos (use find_installments).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond annotations: only manual recurrences are returned, Open Finance connections yield empty results, and installments are excluded. It does not cover pagination or ordering, but that is a minor gap for a zero-parameter list tool.
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: it states the main purpose and examples first, then adds scope limitations and sibling alternatives. Every sentence earns its place, and the exclusions are stated crisply.
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 zero-parameter read-only list tool with no output schema, the description is complete: it states what is returned, what is not returned, the Open Finance empty-result behavior, and the sibling tools to use instead. An agent has enough information to select and invoke it correctly.
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?
The tool has zero parameters and schema description coverage is 100%, so there is no parameter documentation burden. The description instead clarifies what the returned list represents, which is appropriate and useful.
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 names a specific verb and resource: lists registered recurring/infinite transactions (rent, subscriptions, salary) with periodicity, value, and next occurrence. It clearly differentiates the tool from siblings by explicitly excluding installments and pointing to find_subscriptions and find_installments.
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 when-to-use guidance: use it for manually registered recurring accounts/cards, expect empty results for Open Finance-connected accounts, and use find_subscriptions for subscriptions and find_installments for installments. This directly routes the agent to the correct sibling tools.
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.