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 indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral details: it returns authenticated:true and empty pending[] when connected, and connect_url when credentials are missing. This context goes beyond annotations without contradiction.
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 sentences that are front-loaded with the main purpose. Every sentence adds value, 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?
Given no parameters, rich annotations, and simple output structure, the description fully explains the tool's behavior for the two main states. It mentions return fields (authenticated, pending, connect_url) without needing an output schema.
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 tool has zero parameters, so baseline is 4. The description does not need to explain parameters, and it correctly refrains from adding irrelevant info.
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 it returns connection status and URLs, and distinguishes between two scenarios: when all providers are connected and when credentials are missing. It uses specific terms like 'authenticated:true' and 'pending[]', making the purpose precise and distinct from sibling tools like 'authenticate'.
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 implies usage for checking connection status but does not explicitly state when to use this tool versus alternatives like 'authenticate'. There is no guidance on exclusions or prerequisites.
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 clearly separated by resource and action—accounts, transactions, bills, loans, investments, and connection status—so an agent can usually tell them apart. A few pairs remain confusable, notably openfinance_list_transactions vs openfinance_list_transactions_by_item and the monolithic marketplace tool overlapping with report_bug, but the detailed descriptions largely resolve the boundaries.
The openfinance_* subset follows a consistent snake_case verb_noun convention (list_accounts, get_item_status, update_transaction_category), and non-openfinance tools like report_bug and show_version fit the same style. The pattern breaks with bare verbs/nouns such as connect, authenticate, marketplace, and toolkit_info, but the domain prefix makes the majority predictable.
25 tools sits at the top of the heavy-but-manageable range, and the Open Finance resource pairs plus platform/marketplace tools each earn some place. The count feels slightly bloated because marketplace bundles many capabilities and several status/sync tools could be consolidated, but the scope is broad enough that the number is defensible.
The toolkit covers the core Open Finance surface thoroughly: accounts, balances, transactions, credit-card bills, loans, investments, categories, connection lifecycle, sync, and provider health, plus marketplace and platform plumbing. Minor gaps exist—no direct connect-bank action beyond URLs, no per-transaction get endpoint, and some marketplace operations are only accessible through the single marketplace tool—but standard workflows are not dead-ended.