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 and idempotentHint=true, so the safety profile is known. The description adds value by specifying the exact data returned (MCPs, status, accounts, catalog tool counts), which gives the agent a concrete expectation of the output. No hidden side effects are suggested, and the description aligns with 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, well-structured sentence that front-loads the main purpose ('Returns the current toolkit state') and then lists specific components. Every word contributes meaning; there is no fluff or repetition of annotations.
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 (zero parameters, no output schema), the description provides a complete picture. It lists every category of information returned, so the agent knows exactly what to expect. No additional behavioral or output details are necessary for such an introspection tool.
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 there are no parameter semantics to clarify. The description correctly omits any parameter details, and the schema already covers everything with 100% coverage. The baseline of 4 is appropriate because no additional parameter context is needed.
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 states a specific verb ('Returns') and resource ('current toolkit state'), and enumerates the exact contents (installed MCPs, connection status, accounts, catalog tool counts). This clearly distinguishes it from sibling tools like authenticate or connect, which perform actions rather than report state.
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 when to use this tool: whenever an agent needs an overview of the toolkit's current state. It does not explicitly exclude alternatives, but the sibling tools are all action-oriented, so the context is clear. No explicit exclusions are needed for this introspection tool.
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 tools are mostly distinct in purpose: the certificate consultation tool is clearly separate from authentication, connection status, marketplace, and feedback tools. Minor overlap exists between 'connect' and 'toolkit_info' regarding connection status, but descriptions clarify their roles.
Tool names mix languages (Portuguese and English) and conventions: 'certidao_debitos_pj_consultar' uses Portuguese snake_case with noun_verb order, while others like 'authenticate', 'connect', 'marketplace', and 'report_bug' are English verbs or nouns. There is no consistent verb_noun pattern across the set.
Although 7 tools is within a typical range, most are generic MCP platform utilities (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) that are unrelated to the server's stated purpose of issuing federal debt certificates. The core domain is served by only one tool, making the set feel padded and unfocused.
The primary operation—consulting the joint federal debt certificate via CNPJ—is fully covered by 'certidao_debitos_pj_consultar'. For the narrow stated purpose, no obvious dead-ends exist. Additional supporting operations (e.g., historical queries, certificate validation) could be added but are not essential given the tool's description.