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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it's a safe read operation. The description adds valuable behavioral context: it details the two scenarios (all connected vs missing credentials) and what the return values look like (authenticated:true vs connect_url). This goes beyond the 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 two sentences long, front-loaded with the core purpose, and adds essential details without filler. Every sentence is concise and earns its place.
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 parameters and no output schema, the description covers the two main states (all connected vs missing credentials). It does not handle partial connection explicitly, but for a simple status check tool, it is sufficiently complete. The annotations cover safety, and the description adds return behavior.
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?
There are zero parameters and schema coverage is 100%, so the baseline is 4. The description does not need to add parameter semantics since none exist.
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 returns connection status and URLs. It specifies conditional behavior (all connected vs missing credentials), distinguishing it from sibling tools like authenticate (which handles authentication) or openfinance_list_connections (which lists connections). The verb 'returns' and resource 'connection status and URLs' are specific and unambiguous.
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?
The description explains what the tool does but does not explicitly state when to use it versus alternatives like authenticate or openfinance_list_connections. There is no guidance on when not to use it or which scenarios are best suited for this tool. The usage context is implied but not directly articulated.
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 openfinance_* tool targets a distinct resource (account, transaction, bill, loan, investment) with a clear action (get/list/update/force_sync). The administrative tools (connect, authenticate, report_bug) are clearly separate. No two tools appear to perform the same function.
The openfinance_* tools follow a consistent verb_noun pattern (e.g., get_account_balance, list_transactions, update_transaction_category). Minor deviations like openfinance_provider_status (lacks a verb) and openfinance_force_sync (verb phrase) slightly break the pattern, but the overall convention is predictable.
25 tools is on the higher end but appropriate for a comprehensive Open Finance server covering accounts, transactions, bills, loans, investments, connections, and administration. Each tool has a distinct purpose and none feel redundant.
The tool surface is complete for the domain: it covers connection management (connect/disconnect/force sync/status), account and transaction queries, credit card bills, loans, investments, and transaction categorization, plus admin utilities. No obvious gaps that would block typical workflows.