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 read-only and non-destructive behavior. The description aligns with this and adds no conflicting information, giving a clear and consistent picture.
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 with the key action (Returns) front-loaded and all relevant details included without extraneous words.
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 has no parameters and a straightforward read operation, the description fully outlines the returned information, making it complete in context.
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 input schema has no parameters, so there is nothing to describe. The description appropriately focuses on the output and requires no parameter explanations.
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 the toolkit state, listing specific details (installed MCPs, connection status, accounts, catalog counts). This distinguishes it from siblings like authenticate and connect.
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 explains what the tool does but does not explicitly state when to use it versus alternatives, nor provide any usage conditions or 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.
Tools are mostly distinct, but 'authenticate' and 'connect' overlap in purpose (both dealing with auth/connection). The rest are clearly separated by function.
Naming is inconsistent: single-word verbs (authenticate, connect, marketplace) mixed with underscore-separated compound names (pref_ba_camacari_cnd_consultar, toolkit_info). No clear pattern.
Seven tools is a reasonable number for a utility server that includes meta tools and one domain-specific query. Not excessive or minimal.
The server focuses on a single municipal certificate query, but lacks additional domain operations (e.g., listing certificates or status checks). The utility tools are general but not domain-specific, so coverage feels thin for the stated purpose.