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 indicate readOnlyHint=true and idempotentHint=true. The description adds valuable behavioral context: explains the two possible states (authenticated:true with empty pending[] vs connect_url returned). This is 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?
The description is two sentences, front-loaded with the main purpose, and conveys all necessary information without any wasted words. Every sentence 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 use cases. It could potentially mention other states (e.g., partial connection), but for a simple status check it is sufficiently complete.
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 exist, so schema coverage is 100%. According to guidelines, baseline for 0 parameters is 4. The description does not need to add parameter semantics as there are none.
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 behavior for two scenarios (all connected vs missing credentials). The verb 'returns' and resource 'connection status and URLs' are specific. Among siblings like authenticate or marketplace, this tool's purpose is distinct.
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 guide when to use this tool over alternatives like authenticate or openfinance_provider_status. No exclusions or when-not-to-use advice is provided.
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.
Several tools have overlapping purviews—list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and connect vs list_connections vs get_item_status vs provider_status—so an agent could pick the wrong one. The very detailed descriptions disambiguate them, but the tool names alone do not.
The openfinance_ prefix provides a clear family and most members use list_/get_/update_ verbs, but there are deviations like openfinance_provider_status (no verb), openfinance_disconnect_bank, and openfinance_force_sync. Platform tools (authenticate, connect, marketplace, toolkit_info) follow a different, less uniform style.
At 25 tools, this sits at the top of the heavy range. Most Open Finance operations are justified given the breadth of banking data, but overlapping tools and the mega-marketplace tool with many sub-actions make the set feel slightly bloated.
The Open Finance surface covers list/get/update/disconnect/sync for accounts, transactions, credit card bills, loans, and investments, plus provider health, connection search, and platform-level auth, marketplace, version, and feedback. There are no obvious dead ends or missing lifecycle operations.