show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Prefeitura PA Belém: Multas
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, providing the safety profile. The description adds no further behavioral details beyond the resource being shown, which meets the lower bar set by good annotations.
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 directly states the tool's function without unnecessary words or repetition.
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 zero-parameter, read-only informational tool, the description fully covers what the tool returns: platform and adapter versions. No output schema is needed, and the description is sufficient for an agent to select and invoke it.
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?
There are 0 parameters, and schema coverage is 100%, so the description does not need to explain parameter details. The baseline of 4 applies as no parameters exist to document.
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 resources ('MCP platform and adapter versions'). This distinguishes the tool from siblings like 'toolkit_info' which likely covers broader information.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives such as 'toolkit_info'. The description implies a simple version check but does not state exclusions or alternative tools.
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
B3.4/5.0
Disambiguation5/5
Each tool has a clear, distinct purpose: authenticate handles login, connect shows connection status, marketplace finds and runs other MCPs, report_bug sends feedback, show_version displays versions, toolkit_info reports toolkit state, and the domain tool consults fines. No two tools could be easily confused.
Naming Consistency2/5
Tool names mix styles: verb-based names (authenticate, connect, report_bug, show_version), noun-based (marketplace, toolkit_info), and a long descriptive domain name (pref_pa_belem_multas_consultar). No consistent verb_noun pattern or style coherence.
Tool Count3/5
There are 7 tools, which is a reasonable count, but the vast majority are generic platform utilities (authenticate, connect, marketplace, etc.) unrelated to the server's apparent purpose of handling Belém traffic fines. Only one tool actually performs the domain function, making the set feel like a platform wrapper rather than a focused domain server.
Completeness1/5
The domain of traffic fines is severely under-covered: only a single consultation tool exists, with no create, update, or delete operations. The other tools address platform management but do not contribute to the stated purpose of the server, leaving the domain surface incomplete.