show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Prefeitura BA Salvador: 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.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, and non-destructive behavior. The description aligns with these and adds that it retrieves current state, but does not provide extra detail on side effects (none expected).
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?
Description is a single, concise sentence that fully conveys the tool's purpose without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is complete for usage, though it does not specify the output format or structure. Given the simplicity and typical expectation of a version query, this is acceptable.
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?
There are no parameters; schema coverage is complete, and no further explanation is needed.
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?
Description clearly states the tool shows current MCP platform and adapter versions, with a specific verb and resource, making its purpose unambiguous.
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 description implies when to use it (when version info is needed), but it does not explicitly mention alternatives or when not to use it. Context is clear enough for a simple query tool.
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.6/5.0
Disambiguation3/5
Most tools have distinct purposes (auth, marketplace, version, etc.), but 'authenticate' and 'connect' overlap in the authentication/connection space, and the descriptions are verbose enough to clarify, yet some ambiguity remains.
Naming Consistency2/5
Naming convention is inconsistent: generic lowercase names (authenticate, connect) mix with a long prefixed domain tool (pref_ba_salvador_cnd_consultar) and camelCase (toolkit_info), showing no clear pattern.
Tool Count3/5
With 7 tools, the count is reasonable, but most are platform-level utilities unrelated to the server's stated domain (CND consultation), making the set feel bloated with generic functions.
Completeness2/5
The domain coverage is severely lacking: only one tool (pref_ba_salvador_cnd_consultar) addresses the core purpose, with no supporting operations (e.g., list certificates, verify status, handle errors) to make it a complete service.