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, idempotentHint, and destructiveHint, and the description adds meaningful behavioral context by specifying what the state includes (MCPs, connections, accounts, tool counts). This goes beyond the annotations without contradicting them.
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 efficiently enumerates the returned state components. Every word contributes value, with no redundancy or filler.
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?
With no output schema, the description fully covers the return value by listing all key categories of information. The tool is simple (no parameters, read-only), and the description is sufficient for an agent to understand what it will receive.
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 is 4. The description does not need to explain parameters, and the schema having no properties is consistent. No additional semantic information is required.
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 the current toolkit state with specific details (installed MCPs, connection status, accounts, catalog tool counts). This is a specific verb+resource and is clearly distinct from sibling tools which focus on financial operations or 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 when needing toolkit state, but does not explicitly state when to use this tool versus alternatives or name any exclusions. There is no comparison with sibling tools like show_version or provider_status, leaving usage context implied rather than explicit.
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.
Each tool has a clearly distinct purpose. The Open Finance tools are granular (e.g., list vs get vs force_sync for different resources), and the marketplace, authentication, and utility tools do not overlap. No two tools could be easily confused.
The Open Finance tools consistently use the 'openfinance_' prefix followed by a verb_noun pattern (e.g., list_accounts, get_balance). Other tools (authenticate, connect, marketplace) use simple verb names, which is a minor deviation but still clear and predictable.
25 tools is on the higher end, but the server covers a broad domain (marketplace + comprehensive Open Finance operations). Each tool serves a specific function, and the count is justified by the depth of functionality.
The toolset provides full lifecycle coverage for the Open Finance domain: list, get, sync, update, transactions, categories, investments, loans, credit cards, and connections. The marketplace tool is also feature-rich. No obvious gaps for the intended purpose.