Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
| 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=true, idempotentHint=true, and destructiveHint=false, so the read-only nature is covered. The description adds that it reflects the current toolkit state and specifies the output components, but does not mention potential latency, caching, or failure modes. This is adequate given the annotation coverage.
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 a single, front-loaded sentence that states the main verb and result, with every phrase adding meaningful detail about the returned information without any wasted words.
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 zero-parameter tool with no output schema, the description fully enumerates what will be returned (installed MCPs, connection status, accounts, catalog tool counts). Annotations cover the safety profile, and the tool's simplicity means no further context is required.
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?
The tool has zero parameters, so the baseline of 4 applies. The description correctly avoids parameter details since none exist.
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?
Uses the specific verb 'Returns' to state the action and lists exact content: installed MCPs, connection status, connected accounts, and catalog tool counts. This clearly distinguishes it from sibling tools, which are mostly action-oriented (e.g., connect, openfinance_list_accounts).
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 a use case (checking toolkit state) but does not explicitly state when to use it vs alternatives or provide exclusions. As a unique meta-info tool, no alternative is named, but the purpose is clear enough to infer usage.
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 tools have distinct purposes, especially with the openfinance_ prefix grouping banking operations. However, pairs like openfinance_list_accounts vs openfinance_get_accounts_detail and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills could cause minor confusion, though descriptions help.
Tools consistently use snake_case with a clear verb_noun pattern. Open finance tools all start with openfinance_, and utility tools use simple verbs like authenticate, connect, report_bug. No mixing of conventions.
At 24 tools, the count is on the higher side of the borderline range. The server combines platform management (6 tools) and banking operations (18 tools), which justifies the number, but it feels slightly heavy for a single server.
The tool surface covers all major banking operations (accounts, transactions, credit cards, investments, loans) and includes essential maintenance tools (sync, status, disconnect, search connectors). Platform management is also comprehensive with authentication, marketplace operations, and diagnostics.