show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Prefeitura BA Ilheus: Certidão Negativa de Débitos
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.8/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations explicitly indicate readOnlyHint: true, idempotentHint: true, and destructiveHint: false, aligning with the 'Show' action in the description. No mutating or risky behavior is implied.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that fully conveys the tool's function. No extraneous details or complex structure is needed for such a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool and the comprehensive annotations (read-only, idempotent, non-destructive), the description is complete. No output schema is necessary since the tool returns version info as a simple result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there are no parameter ambiguities. The schema is empty, and the description covers everything, achieving 100% coverage trivially.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: showing the current MCP platform and adapter versions. This is unambiguous and directly reflects the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The tool has no parameters and its use case is self-evident from the description. It doesn't specify when to use it, but for a simple version query, such guidelines are unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation3/5
Several tools overlap in the authentication/connection space (authenticate, connect, toolkit_info), and the massive marketplace tool dwarfs the single domain-specific tool. An agent may struggle to choose the right tool for routine setup vs. actual certificate consultation.
Naming Consistency2/5
Tool names mix bare verbs (authenticate, connect), nouns (marketplace), a Portuguese descriptive phrase (pref_ba_ilheus_cnd_consultar), and compound verbs (report_bug, show_version). No consistent verb_noun pattern is followed.
Tool Count2/5
Seven tools is numerically reasonable, but six are generic platform utilities unrelated to the server's stated purpose. The actual domain-specific functionality is reduced to a single tool, making the set feel bloated and misaligned.
Completeness3/5
The domain of issuing a negative certificate is served by one core consultation tool, but no additional domain operations (e.g., certificate history, validation, cancellation) exist. The platform tools add unrelated breadth rather than filling domain-specific gaps.