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 readOnlyHint, idempotentHint, and destructiveHint false, providing safety profile. Description adds value by disclosing conditional behavior: returns authenticated:true/pending[] when all providers connected, or connect_url when credentials missing. This context 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 concise sentences, zero waste. Front-loaded with purpose, then conditional details. 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 output schema, description explains return values in two scenarios (all connected vs missing credentials). Complete enough for a simple status check tool, but might benefit from mentioning whether other states exist or format of URLs.
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?
Tool has 0 parameters, so baseline score is 4. Description adds no parameter info (not needed), and schema coverage is 100%.
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?
Description clearly states verb 'returns' and resource 'connection status and URLs'. It distinguishes from siblings like 'authenticate' (auth flow) and 'openfinance_get_item_status' (specific item status), positioning itself as the overall connectivity check.
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?
Usage is implied: use to check connection status. However, no explicit guidance on when to use vs siblings (e.g., when to prefer authenticate or specific status tools). No when-not-to-use or alternatives mentioned.
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 openfinance_* tools target distinct resources and actions, but several overlap in purpose: list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and multiple connection/status tools expose reconnect URLs. The long descriptions help, but the boundaries are not always immediately obvious.
The openfinance_* tools follow a consistent list_/get_ verb_noun pattern and share a clear prefix. The smaller platform cluster is less consistent — marketplace, connect, authenticate, show_version, toolkit_info — mixing nouns, bare verbs, and snake_case, but it is a minor deviation overall.
At 25 tools, this sits at the heavy end of acceptable. The Open Finance surface is broad enough to justify many of them, but there is redundancy (e.g. list_transactions_by_item largely wraps list_transactions plus account resolution) and a separate platform-management cluster that makes the set feel sprawling.
The Open Finance domain is well covered: connection lifecycle, accounts, balances, transactions, credit-card bills, loans, investments, categories, and provider status are all present, and data flows connect properly between tools. Minor gaps exist, such as no single-transaction fetch or dedicated prompt-management tools, but the marketplace tool fills those roles.