show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
JUCESP: Ficha Cadastral Simplificada
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no extra behavioral context beyond what the annotations provide, but it does not contradict them either.
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 immediately states the tool's function with no filler or redundant details.
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?
For a trivial version-information tool with no parameters, no output schema, and strong annotations, the description fully covers what the tool does and requires no additional explanation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so parameter descriptions are unnecessary. The baseline of 4 for no params is appropriate; the description adds no parameter information because none exists.
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 uses a specific verb ('Show') and clearly identifies the resource ('current MCP platform and adapter versions'). It is distinct from sibling tools like authenticate or report_bug, which have obviously different purposes.
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 usage context is clear: use this tool to retrieve version information. It does not explicitly mention alternatives or when-not-to-use, but for a zero-parameter informational tool this is not a significant omission.
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
Disambiguation2/5
The tools have significant overlap: 'authenticate' and 'connect' both handle login/connection status, while 'marketplace' and 'toolkit_info' both describe platform capabilities. The verbose descriptions further blur distinctions, making it hard for an agent to choose the right tool.
Naming Consistency1/5
Naming is highly inconsistent: mixed languages (Portuguese 'jucesp_ficha_consultar' vs English 'authenticate', 'marketplace'), mixed verb/noun forms, and no clear pattern. The tool names range from imperative verbs to descriptive nouns without a unifying convention.
Tool Count3/5
The count of 7 tools is within a reasonable range, but the set includes many generic platform tools (marketplace, report_bug, show_version) that are unrelated to the core JUCESP domain, making the count feel inflated relative to the actual purpose.
Completeness2/5
For a JUCESP company registry consultation, there is only one domain-specific tool (jucesp_ficha_consultar). The rest are generic platform utilities, so the tool surface is missing common operations like search, list, or update for the registry data, leaving significant gaps for the stated purpose.