Lists loan contracts per bank connection (GET /loans). Pass items as an array of connection selectors (item_id uuid, connector_id, or connector_name) — one entry per connection to fetch; multiple connections are queried sequentially with rate-limit spacing. OMIT items to list loans across ALL linked banks. Returns { results, errors } per connection.
| Name | Required | Description | Default |
|---|---|---|---|
| items | No |
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 valuable context: sequential per-connection execution, rate-limit handling, and return structure of `{ results, errors }`. No contradiction 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 concise—three sentences—front-loaded with the purpose. Every sentence adds essential information: endpoint, parameter behavior, and return format. 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 no output schema, the description includes the return format `{ results, errors }` per connection. Combined with annotations covering safety and idempotency, the description provides sufficient context for an agent to correctly use this tool without ambiguity.
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?
Schema description coverage is 0%, so the description bears the full burden. It thoroughly explains the sole parameter `items`: it's an array of connection selectors (item_id uuid, connector_id, or connector_name), one per connection, and the effect of omitting it. This fully compensates for the lack of schema descriptions.
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 loan contracts per bank connection, mentions the HTTP method and endpoint (GET /loans), and distinguishes from sibling tool openfinance_get_loan_detail by specifying it returns multiple contracts per connection.
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 clear guidance on when to omit or pass the `items` parameter (omit for all banks, pass per connection). Mentions sequential querying with rate-limit spacing. However, it does not explicitly state when to use this tool over siblings like openfinance_get_loan_detail for a single loan.
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 openfinance_* tools target distinct resource/action pairs, but there is real overlap among list_accounts, get_accounts_detail, and get_account_balance, as well as between list_transactions and list_transactions_by_item, and between get_credit_card_bill and list_credit_card_bills. The descriptions are detailed enough to usually resolve ambiguity, but the number of near-overlapping read/status tools makes mis-selection plausible.
The 21 openfinance_* tools follow a clear openfinance_<verb>_<noun> convention with predictable verbs like list, get, update, force, disconnect, and search. The non-prefixed platform tools (authenticate, connect, marketlace, report_bug, show_version, toolkit_info) break the pattern but are few enough to keep the naming mostly coherent.
25 tools is at the heavy end for the stated banking domain, and several could reasonably be merged: get_account_balance/get_accounts_detail/list_accounts and list_transactions/list_transactions_by_item overlap in purpose. The breadth of resources covered accounts, cards, loans, investments, connections, and provider health helps justify the count, but it still feels slightly bloated.
The Open Finance workflow is thoroughly covered: connect discover, force sync, status checks, accounts, balances, transactions, credit-card bills, loans, investments, category correction, disconnection, and provider health. Edge cases like stale data, consent errors, provider incidents, and cross-connector asymmetries are explicitly handled, leaving no obvious dead ends for an agent.