show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DETRAN AM: 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 read-only, idempotent, and non-destructive behavior; the description adds 'current' but doesn't elaborate on side effects or output characteristics beyond that.
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, focused sentence with no unnecessary words, making it highly concise.
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?
For a simple information tool, the description is adequate, but it could specify what the returned version information includes (e.g., format or fields) to be more complete.
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 has zero parameters, so the description fully covers parameter usage; no additional explanation 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?
The description clearly states the tool shows current MCP platform and adapter versions, making its purpose unambiguous and distinct from sibling tools like toolkit_info.
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?
The description provides no guidance on when to use this tool versus alternatives (e.g., toolkit_info), leaving the selection context unclear.
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.2/5.0
Disambiguation2/5
Several tools have overlapping purposes: 'authenticate' and 'connect' both deal with login/connection status, while 'marketplace' is a sprawling meta-tool that covers searching, describing, invoking, installing, and managing prompts—it overlaps with 'report_bug' (feedback) and 'show_version' (platform info) in providing platform functionality. The DETRAN-specific tool is distinct, but the rest are not cleanly separated.
Naming Consistency2/5
Tool names are a mix of single-word verbs ('connect', 'authenticate', 'marketplace'), snake_case Portuguese for the DETRAN tool, and hyphenated terms like 'report_bug' and 'show_version'. The naming is inconsistent in style and doesn't follow a predictable verb_noun pattern, making it harder to infer what each tool does from its name alone.
Tool Count3/5
Seven tools is within a reasonable range for a server, but the count is misleading: the 'marketplace' tool aggregates many distinct capabilities (search, describe, invoke, install, prompts) into one tool, which inflates the apparent coverage while the actual set of distinct functions is smaller and less cohesive.
Completeness2/5
The server's primary domain appears to be querying DETRAN AM fines, but aside from the single consultar tool, there's no support for other lifecycle operations (e.g., payment, dispute, or history). The other tools are platform utilities, not DETRAN-specific, so the surface is incomplete for the stated purpose of the server.