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?
Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), description adds important behavioral details: sequential processing with rate limiting, return structure `{ results, errors }`, and the effect of omitting `items`. No contradictions.
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, front-loaded with the core purpose. Every word earns its place. Efficient and clear.
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's simplicity (1 optional parameter, no output schema, clear annotations), the description fully covers behavior, parameter semantics, and return type. No gaps.
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 schema has 0% description coverage, but the description explains that `items` is an array of connection selectors (item_id, connector_id, or connector_name) and the behavior of omitting it. This adds crucial meaning not present in the raw schema.
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 (GET /loans)', specifies the HTTP method and endpoint, and distinguishes from sibling tools like openfinance_get_loan_detail by indicating it lists multiple loans. The behavior with the `items` parameter is explicitly defined.
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 explicit guidance on when to pass `items` (to list specific connections) and when to omit it (all banks). Mentions sequential querying with rate-limit spacing. Lacks explicit exclusion of alternatives, but the context is clear enough.
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.
The openfinance_ tools are mostly distinct by resource/action, but there are several overlapping pairs: list_accounts vs get_accounts_detail, list_credit_card_bills vs get_credit_card_bill, list_transactions vs list_transactions_by_item, and connect vs toolkit_info vs openfinance_list_connections. The descriptions help disambiguate, but an agent could still misselect between these related tools.
The core banking tools consistently follow an openfinance_<verb>_<noun> pattern, which is a strong and readable convention. The generic platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break that pattern and use mixed naming styles, creating two distinct naming tiers within the same server.
25 tools sits at the upper borderline of what feels reasonable for one server. The Open Finance domain justifies many read/query tools, but the inclusion of platform meta-tools like marketplace, connect, toolkit_info, report_bug, and show_version inflates the count beyond a tightly focused bank-data scope.
The Open Finance surface is largely complete: connectors, sync, disconnect, accounts, balances, transactions, categorization, credit card bills, loans, investments, and provider status are all covered. Minor gaps exist, such as the lack of a dedicated investment detail endpoint and limited consent/permission introspection, but agents can work around these with the existing tools.