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, covering the safety profile. The description adds valuable context on what the returned state includes, which goes beyond the annotations and clarifies the tool's output scope.
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 lists the key components of the returned state without wordiness. Every element earns its place, making it easy to scan and understand.
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 low complexity, rich annotations, and no parameters, the description fully captures what the tool returns. It is complete for an agent to select and invoke the tool correctly without needing additional details.
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, and the empty input schema makes this obvious. Per the rubric, a baseline of 4 is appropriate; the description need not explain parameters and instead focuses on the output, which is sufficient.
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 uses a specific verb ('Returns') and resource ('current toolkit state') and enumerates the content (installed MCPs, connection status, accounts, catalog tool counts). This clearly distinguishes it from siblings like show_version or authenticate, making the purpose unmistakable.
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 for checking overall toolkit state but does not explicitly state when to use it versus alternatives like show_version. No exclusions or alternative tool names are mentioned, so guidance is only implied.
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 clear purposes, but 'authenticate' and 'connect' both deal with authentication state, and 'marketplace' overlaps slightly with 'toolkit_info' in terms of discovering vs. viewing tools. These pairs could cause initial confusion, though descriptions help.
Names mix English verbs (authenticate, connect, report_bug) with a noun (marketplace) and a Portuguese command (fincen_consultar). There is no consistent verb_noun or noun pattern, making the set feel ad hoc.
With 7 tools, the number is well within the typical range for a platform server. Each tool serves a distinct functional area (auth, status, query, marketplace, bug, version, toolkit), so none feels superfluous.
The platform covers essential operations: authentication, connection status, tool discovery/execution, bug reporting, version info, and toolkit state. The FinCEN-specific side is minimal (one query tool), but the marketplace allows extending coverage, so the surface is reasonably complete.