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 provide readOnlyHint=true and destructiveHint=false, so safety is clear. The description adds value by enumerating the specific categories of information returned (installed MCPs, connection status, accounts, catalog tool counts), which coordinates with the no-parameter schema. No contradiction.
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 packs all relevant information without filler. It is front-loaded with the main purpose ('Returns the current toolkit state') and then elaborates with a concise enumeration of what that includes.
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 zero-parameter, read-only info tool with strong annotations, the description is complete. It tells the agent what the tool will report, covers the scope, and there are no missing parameters or behavioral caveats to document. The presence of siblings like 'show_version' further clarifies that this is a broader state report.
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 and schema coverage is 100% (empty properties). The description doesn't need to explain parameters; it focuses on the return content, which is the primary value. A baseline of 4 is appropriate for tools with no parameters that still describe what is returned.
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, specifying exactly what is included: installed MCPs, connection status, connected accounts, and the number of catalog tools each exposes. This distinguishes it from siblings like 'show_version' (version only) and 'connect' (connection action).
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 is a read-only informational tool for inspecting the toolkit's current state. It doesn't explicitly state when to use it versus siblings, but the context is clear enough given its purpose. It doesn't mention exclusions or alternatives, but the informational role is evident.
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 distinct purposes, but marketplace is a multi-purpose hub that overlaps with connect and toolkit_info for managing MCPs and could confuse agents discerning current state vs. discovery/run capabilities. The primary domain tool (detran_pb_licenciamento_consultar) is clear, but the platform-level tools have some boundary overlap.
Naming is inconsistent: some tools use snake_case verbs (detran_pb_licenciamento_consultar, show_version, report_bug), some are single-word nouns without verbs (connect, marketplace, toolkit_info), and one uses an imperative (authenticate). There is no consistent verb_noun pattern across the set.
7 tools is a reasonable count for a server that combines a specific domain query tool with platform meta-tools (auth, marketplace, bug reporting, version checks). It is slightly heavy because several tools are housekeeping rather than domain features, but still within an acceptable range.
The domain surface is severely limited: only one tool for the stated purpose (consulting DETRAN PB licensing), with no supporting tools for fetching details, history, or related vehicle operations. The remaining tools focus on platform management rather than the domain, making the server feel incomplete for its primary claim.