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 |
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, idempotentHint, destructiveHint. Description adds value by detailing sequential querying with rate-limit spacing and return structure {results, errors}, beyond what annotations provide.
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 purpose, no wasted words. Efficient and well-structured.
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 mentions return structure and covers both use cases (specific connections vs all). Complete for a list operation.
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 has 0% description coverage, but the description fully explains the `items` parameter: it accepts an array of connection selectors (item_id, connector_id, or connector_name) and the effect of omitting it. This compensates completely.
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 the tool lists loan contracts per bank connection using the GET /loans endpoint. It distinguishes from siblings like openfinance_get_loan_detail by specifying 'per bank connection' and the batch behavior.
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 usage context: how to optionally pass `items` for specific connections or omit for all. While it doesn't explicitly list when-not-to-use or alternatives, the guidance is practical and sufficient.
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 are clearly separated by resource and action, and the long descriptions help, but several pairs can trip up an agent: authenticate/connect both deal with login/connection state, openfinance_list_transactions and openfinance_list_transactions_by_item sound nearly identical, and marketplace internally exposes report_bug/list_tools functions that also exist as top-level tools. This is more than a single ambiguous edge.
The 19 openfinance_* tools follow a clean get_/list_/update_ pattern and are easy to navigate, but the platform-level tools break the convention: authenticate, connect, marketplace, toolkit_info, report_bug, and show_version mix bare verbs, nouns, and noun-noun compounds. The pattern is not chaotic, but it is definitely mixed.
25 tools is on the heavy end of the borderline range and is a large working set for an agent. The openfinance tools are individually justified and support batching, but the extra platform/marketplace tools add scope and some redundancy with report_bug and toolkit_info.
For a bank-data aggregation server, the surface is complete: connector discovery, linking/reconnecting/disconnecting, account lists and details, balances, transactions, categorization, credit-card bills, investments, loans, sync status, and provider health are all covered. There are no obvious dead ends in the main workflows.