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 provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds sequential query behavior with rate-limit spacing and return format ({results, errors} per connection). No contradiction.
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?
Three sentences: purpose, parameter usage, return format. No unnecessary words, front-loaded with main action.
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?
Covers purpose, parameter semantics, optional behavior, rate-limit handling, return format. No output schema needed since return described. Complete for agent to use tool 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?
Input schema has one optional array parameter with 0% description coverage. Description fully explains 'items' as connection selectors (item_id, connector_id, connector_name) and behavior when omitted.
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 'Lists loan contracts per bank connection' with endpoint (GET /loans). Distinguishes between listing specific connections and all connections. Differentiates from sibling tools like openfinance_get_loan_detail and openfinance_list_accounts.
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?
Explicit guidance: pass 'items' for specific connections, omit for all. Mentions rate-limit spacing for multiple connections. Lacks explicit exclusion of alternatives, but parameter guidance is clear.
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.
Each tool targets a distinct resource and action, with clear separation between general server utilities (authenticate, connect, marketplace) and the openfinance_* family (get/list/search/update per domain). No two tools appear to overlap: list_transactions vs list_transactions_by_item are differentiated by granularity, and get_item_status vs provider_status by scope. The marketplace tool, while broad, is explicitly named and described, so it doesn't cause ambiguity.
All 20 openfinance_* tools follow a strict verb_noun snake_case pattern (list_accounts, get_account_balance, force_sync, update_transaction_category, etc.). The five general tools also use snake_case and clear names, maintaining consistency across the set. No mixing of conventions or inconsistent verb styles.
At 25 tools, the set is on the higher end but well-justified for a platform that aggregates Open Finance data and provides a marketplace. The 20 openfinance tools cover distinct banking operations (accounts, transactions, bills, loans, investments, connections, sync, status, search, categories), each addressing a specific need. The 5 general tools handle authentication, connection status, and platform info. No obvious trivial or redundant tools; each earns its place.
The tool surface is comprehensive for the stated domain: CRUD-like coverage across financial resources (list/get for accounts, transactions, bills, loans, investments), plus state management (force_sync, disconnect, update_category) and ecosystem support (search_connectors, provider_status, marketplace). It also includes utilities like authenticate, connect, and version/bug reporting. No missing operations that would cause agent failures; the set covers connection lifecycle, data retrieval, and even API diagnostics.