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. The description adds useful context by specifying the returned data (installed MCPs, connection status, accounts, catalog tool counts). It does not mention any side effects, but annotations cover the safety profile, and the description aligns with 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, well-structured sentence that efficiently conveys all essential information without wasted words. It is front-loaded with the action ('Returns') and provides a clear list of what is included.
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 the tool's simplicity (no parameters, no output schema), the description is complete. It explains what the tool returns and is sufficient for an agent to know when to call it. The sibling context helps situate it among related tools, and the description fully fulfills the informational need.
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 doesn't need to explain parameter semantics because there are none. Schema coverage is 100% (vacuously), and no additional parameter information is necessary.
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's purpose with a specific verb ('Returns') and resource ('current toolkit state'), enumerating the exact contents (installed MCPs, connection status, accounts, catalog tool counts). This distinguishes it from siblings like show_version, which likely only returns version info.
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 provides clear context: use this to obtain an overview of the toolkit's state. It doesn't explicitly mention alternatives or when-not-to-use scenarios, but for a read-only informational tool, the usage is self-evident and doesn't require exclusions.
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.
marketplace and search_tools both provide search/describe/invoke capabilities for the MCP catalog, creating significant overlap. Additionally, connect and toolkit_info both report connection status, leading to boundary confusion between these pairs.
All tool names use lowercase with underscores, but the structural pattern varies: one-word verbs (authenticate, connect), a noun (marketplace), and verb_noun compounds (report_bug, search_tools, show_version, toolkit_info). This is readable but lacks a consistent convention.
Seven tools is well within the ideal 3-15 range for this platform management server, and each tool earns its place in the workflow without feeling bloated or sparse.
The toolkit covers authentication, connection status, catalog discovery/execution, installation/subscription (through marketplace actions), feedback, and versioning. Minor gaps exist in dedicated management operations, but core lifecycle coverage is strong.