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 | |||
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 readonly, idempotent, non-destructive. Description adds context about response format in different states, providing additional behavioral transparency 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, no wasted words. Front-loaded with main purpose, then detail on scenarios.
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 simple status tool with no output schema, the description sufficiently explains the return values for both success and missing credentials cases. Could mention structure of URLs, but overall 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, so baseline 4 applies. Description does not need to add parameter details, and it correctly focuses on behavior.
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, with specific scenarios for when providers are connected or credentials missing. However, it doesn't explicitly differentiate from sibling tools like 'authenticate' or 'openfinance_list_connections'.
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 guidance on when to use this tool versus alternatives, nor when not to use it.
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 target clearly distinct resources (accounts, transactions, bills, loans, investments, connections, categories). Minor overlap exists—list_accounts returns balances and list_transactions_by_item consolidates what list_transactions provides—but the detailed descriptions distinguish them adequately.
The openfinance_* tools follow a consistent verb_noun pattern (get_*, list_*, update_*, force_sync, search_*) with one slight deviation: openfinance_provider_status omits a verb. The non-openfinance platform tools (authenticate, connect, marketplace, report_bug, etc.) break the prefix pattern, creating two naming conventions within the same server.
25 tools sits at the upper boundary of acceptable for a comprehensive Open Finance banking adapter, covering accounts, transactions, credit cards, loans, investments, and connection management. However, including meta-platform tools like marketplace and toolkit_info inflates the count and makes the set feel heavier than a pure banking tool surface.
The tool surface covers the core Open Finance lifecycle well: list/get accounts, balances, transactions, credit card bills, loans, investments, connection management, category correction, and provider status. Gaps include no direct new-bank connection tool (only URLs) and no investment detail endpoint beyond transactions, but agents can work around these.