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 mark the tool as read-only, idempotent, and non-destructive. The description adds behavioral context by detailing exactly what the returned state contains (installed MCPs, connections, accounts, tool counts). No contradictions with annotations exist.
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 sentence that immediately states the verb ('Returns') and resource ('current toolkit state'), followed by a concise enumeration of the state's components. Every phrase earns its place with no redundancy.
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 (no parameters, no output schema), the description is fully complete: it tells the agent exactly what to expect from the response. The list of included elements (installed MCPs, status, accounts, catalog tool counts) adequately covers the tool's purpose.
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 schema provides full coverage (100%) by definition. The description adds meaning by clarifying what the returned state represents, which compensates for the lack of any parameter details.
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 current toolkit state, enumerating specific components: installed MCPs, connection status, connected accounts, and catalog tool counts. This 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 provides clear context for when to use this tool: whenever an overview of the toolkit's current state is needed, including installed MCPs and connection status. It does not explicitly mention exclusions or alternatives, but the purpose is sufficiently distinct from siblings that no further guidance is necessary.
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 distinguishable: the domain query is unique, and platform tools like authenticate, connect, and report_bug have clear roles. However, connect and toolkit_info both report connection status, and marketplace handles a wide range of actions, causing minor overlap.
Names mix verbs (authenticate, connect), nouns (marketplace), and underscores with inconsistent ordering (report_bug vs toolkit_info vs situacao_eleitoral_consultar). There is no uniform verb_noun pattern across the set.
Seven tools is a reasonable count for a platform wrapper with one domain integration. Each tool serves a purpose, though show_version is trivial and marketplace is oversized.
The domain surface is minimal—only a single consult operation for electoral status, which is appropriate for a read-only public query. The platform tools extend capability via the marketplace, but for a dedicated TSE server, additional operations like batch or status checks are missing.