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 declare readOnly and idempotent, and the description adds behavioral context by detailing response content under different conditions (authenticated vs missing credentials). This goes beyond annotations, though it could mention safety for repeated calls.
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, front-loaded with the main purpose, and no wasted words. Every sentence adds value.
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?
The description covers the two main states (connected and missing credentials) adequately for a simple status check tool with no parameters and no output schema. Minor omission: no mention of error states or additional response fields.
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?
Input schema has zero parameters, and the baseline for 0 params is 4. The description does not need to parameter semantics, so this score is appropriate.
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, with specific scenarios (all connected vs credentials missing). It distinguishes from siblings like 'authenticate' which perform actions rather than checking status.
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 use for checking connection status but does not explicitly contrast with siblings or provide when-to-use guidance. No alternatives are mentioned, which would help in selecting this tool among many siblings.
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 open_-finance tools are clearly bound to a resource+action, but several pairs require careful reading: list_transactions vs list_transactions_by_item, get_iate_status vs get_provider_status, and connect vs list_connections. The marketplace tool is also a single heavily overloaded tool that bundles search/describe/invoke/install and a prompt library, which blurs its boundary.
The Open Finance tools follow openfinance_verb_noun consistently, and the top-level tools are all snake_case, so there is no wild con convention mixing. Deviations exist in generic tools like marketplace/toolki_i/nfo and in non-verb patterns like accent_status, but overall the naming is readable and predictable.
At 25 tools the server sits at the upper edge of what is comfortably scoped; the many list/get/status endpoints are justified by the Open Finance domain, but the extra marketplace and admin utilities make it feel broader than a single-purpose sovereign. It is not abusive, but it is definitely on the heavy side.
The Open Finance access covers accounts, balances, transactions, credit card bills, investment, loans, connections, diagnostics, force-sync, and transaction recategorization. Missing operations are mostly intentional autentications/connection widget hand-offs (add_connection_url, reconnect_url), so the set can still support common workflows without dead ends.