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 detail on what is returned, but does not disclose additional behaviors like auth requirements or rate limits. It does not contradict annotations.
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, clear sentence that efficiently captures the tool's purpose and output without any redundant text.
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 tool with no parameters and no output schema, the description provides a sufficient overview of the return content. It could have been more explicit about the exact structure of the returned state, but it covers the key elements.
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?
No parameters exist, and schema coverage is 100%. The description does not need to elaborate on parameters. Baseline for zero-parameter tools is 4.
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 toolkit state with specific details (installed MCPs, connection status, accounts, tool counts). It is distinct from siblings like authenticate or connect, which serve different purposes.
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 this tool is for inspecting toolkit state but gives no explicit 'when to use' or exclusions. It doesn't mention alternatives, though the intended context is clear from the description.
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 clearly distinct purposes, but authenticate and connect both relate to authentication/connection status, which could confuse an agent. The single domain tool (mandados_prisao_consultar) is clearly distinct from the platform utilities.
Names are lowercase with underscores but mix bare verbs (authenticate, connect), verb+noun compounds (report_bug, show_version), and nouns (marketplace, toolkit_info). The Portuguese name mandados_prisao_consultar breaks the English pattern, resulting in an inconsistent though readable set.
With 7 tools, only one relates to the server's stated domain of arrest warrants; the other six are generic MCP platform utilities. This makes the count inappropriate as the platform tools dilute the server's focus and purpose.
The server offers only a single domain operation (mandados_prisao_consultar) and lacks any other warrant-related operations such as listing, detailed lookups, or historical searches. The platform tools are comprehensive for infrastructure but do not contribute to the domain, leaving the core purpose severely incomplete.