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 safety traits (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds behavioral details about return values in different scenarios, which goes 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: first states the purpose, second elaborates on two possible outcomes. No wasted words, well-structured.
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 output schema, the description adequately covers the two possible return states. For a simple status tool with no parameters, it is 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 baseline is 4. The description does not need to add parameter 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 the tool returns connection status and URLs, and explains the two scenarios (all connected vs missing credentials). It distinguishes from siblings like 'authenticate' by focusing on status rather than performing authentication.
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 as a status check tool, but does not explicitly state when to use it versus alternatives or when not to use it. However, the context is clear for a read-only status endpoint.
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 tools are largely distinct, especially the openfinance_* suite which follows clear resource+action patterns. A few could be confused (e.g., openfinance_list_transactions vs openfinance_list_transactions_by_item, or get_account_balance vs list_accounts) but descriptions are thorough and clarify boundaries. The non-prefixed tools (authenticate, connect, marketplace) are also distinct, though 'marketplace' is quite overloaded internally.
The openfinance_* tools follow a very consistent verb_noun pattern (list, get, force_sync, update, search, provider_status). However, the platform tools are heterogeneous: authenticate, connect, report_bug, show_version are verb_noun, but 'marketplace' and 'toolkit_info' are nouns. This mix is a minor inconsistency, but overall the naming is predictable across the two clear groups.
At 25 tools, this is on the heavy side (16-25 is considered heavy), but the breadth is justified by a comprehensive Open Finance API (19 tools) plus platform management (6 tools). Each openfinance_* tool maps to a specific endpoint or operation, so none feel redundant. Slightly above the ideal 3-15 range, but appropriate for a full financial data adapter.
The Open Finance surface is remarkably complete: accounts, transactions, bills, loans, investments, categories, connection management (list, force_sync, status, provider_status, search connectors, disconnect), and even a categorization update. The platform side covers authentication, connectivity, marketplace operations (search/describe/invoke/install/subscribe), bug reporting, version, and toolkit info. No obvious dead ends or missing lifecycle steps.