Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint. Description adds behavioral details about response content in two scenarios (connected vs missing credentials), which goes beyond 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?
Two concise sentences, front-loaded with main purpose. No wasted 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?
For a zero-parameter, read-only tool, description covers the two main response states. Could mention response structure more formally but adequate.
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?
No parameters, schema coverage 100%, so baseline is 4. Description adds context about response, which is sufficient.
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 it returns connection status and URLs, distinguishing two states (connected vs missing credentials). Verb 'returns' plus resource 'connection status' is specific. Siblings like 'authenticate' suggest a different action, though not explicitly contrasted.
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?
Implied usage for checking connection status, but no explicit when-to-use, when-not-to-use, or alternatives. Does not contrast with sibling 'authenticate' or 'openfinance_list_connections'.
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 resources and operations (balance, accounts, loans, investments, connections, provider status), but credit card bill handling is split across three overlapping tools (get_credit_card_bill, list_credit_card_bills, list_transactions), which could cause misselection. The platform-level tools (authenticate, connect, marketplace, etc.) are clearly distinct from the finance tools.
The openfinance_* tools mostly follow a verb_noun snake_case pattern (list_accounts, get_account_balance, update_transaction_category), but a few deviate (openfinance_provider_status, openfinance_search_bank_connectors). The non-prefixed platform tools break the pattern entirely with mixed styles: verbs (connect, authenticate), nouns (marketplace), and noun_verb (report_bug, show_version).
At 25 tools, this sits at the high end of reasonable scope. Each Open Finance tool maps to a specific endpoint or workflow, and the platform tools are needed for the MCP meta-layer, but the sheer number makes the set feel heavy and harder to navigate.
The Open Finance surface is thorough: connection lifecycle, accounts, balances, transactions, credit card bills, loans, investments, categories, and provider health. Minor gaps exist (e.g., no webhook management, no bulk CSV export), but core workflows are well covered and there are no dead ends.