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 indicate readOnly, idempotent, and non-destructive behavior. The description adds specific detail about the content returned (installed MCPs, connection status, accounts, catalog counts), which goes beyond the annotations and provides useful context about the tool's output.
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, concise sentence that directly states the tool's purpose and output. No unnecessary words or fluff.
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 simple read-only query tool with no parameters and no output schema, the description is fully complete. It explains what the tool does and what information it returns, leaving no ambiguity.
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 score of 4 applies. There is nothing to explain about parameters, and the description does not need to cover them.
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 that the tool returns the current toolkit state and enumerates exactly what that includes (installed MCPs, connection status, accounts, catalog tool counts). It is specific and distinguishable from sibling tools like authenticate or connect, which perform actions.
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 that this is a read-only query tool, but it does not explicitly state when to use it versus alternatives. There is no direct guidance on use cases or when not to use it, though its purpose is fairly self-evident for checking state.
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.
The single domain tool is clearly distinct from the platform utilities. authenticate and connect overlap slightly around credentials/connection status, but their descriptions separate login from status checking. No other tools are confusable.
Names mix bare verbs (authenticate, connect), English verb_noun pairs (report_bug, show_version), noun-only names (marketplace, toolkit_info), and a Portuguese snake_case domain verb (detran_go_debitos_consultar). There is no consistent naming convention across the set.
Seven tools is not an excessive number, but six are generic platform/marketplace utilities while only one addresses the server's stated DETRAN GO debts domain. The count is reasonable overall, yet the scope feels mismatched with the server name.
For a debts-consultation server, only one domain operation exists, with no query variety or broader debt-related workflow. The platform tools are fairly complete for managing MCPs, but they do not fill the domain-specific gap implied by the server name.