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 (readOnlyHint, idempotentHint, destructiveHint) indicate safe, read-only behavior. Description adds detail on response structure (authenticated, pending, connect_url) 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 sentences, front-loaded with main purpose. No extraneous information.
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-checking tool with no parameters and no output schema, the description sufficiently covers expected response scenarios.
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 in input schema, and schema coverage is 100%. Description adds no parameter info, which is fine since none exist. Baseline score of 3 applies.
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, and distinguishes between different states (all providers connected vs missing credentials). This differentiates it 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 explains when to expect 'authenticated:true' vs when to use connection URLs, providing context for when to invoke. It could explicitly mention when not to use, but the context is clear.
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 mostly separated by resource and verb, but there are several borderline pairs: list_transactions vs list_transactions_by_item, get_item_status vs list_connections vs provider_status, and list_accounts vs get_account_balance. The marketplace tool also bundles search/describe/invoke/install/report_bug/prompt-library actions, which overlaps with standalone report_bug and adds confusion.
The openfinance_* family follows a clean get_/ list_/ update_ pattern, but the platform tools mix bare verbs like connect and authenticate with noun-style names like marketplace and toolkit_info. This split is readable but not a single consistent convention.
25 tools sits at the upper end of the 16-25 'heavy' band. The Open Finance domain genuinely has many resources and the openfinance_* tools mostly earn their place, but the generic platform tools plus the multi-purpose marketplace make the set feel larger than its core purpose requires.
The Open Finance lifecycle is well covered: connection search/link/status/sync/disconnect, accounts/balances/detail, transactions with categorization, credit-card bills with derived payment status, loans, and investments with transaction history. Minor gaps exist, such as no standalone connect/install tools, but those flows are handled via URLs and embedded marketplace actions rather than missing entirely.