show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Consulta de Multas
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description doesn't need to repeat safety. It adds context about the specific versions reported but does not describe any potential delays or response format nuances.
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?
Single, complete sentence with no filler. It is front-loaded and immediately conveys the purpose.
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 simple version query with no parameters and no output schema, the description is fully adequate. It tells the user exactly what information will be provided.
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 there is nothing to explain. The schema covers everything by having an empty properties object. Baseline for no parameters is 4, and the description aligns with this.
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. Verb 'Show' is specific, and it identifies the exact resource, distinguishing it from siblings like 'toolkit_info' which likely covers broader info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when version information is needed, but it does not explicitly mention when not to use it or alternatives. Sibling tools like 'toolkit_info' might serve similar purposes, but no guidance is provided.
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
The five multa-related tools are clearly distinct by resource (vehicle debts, history, federal infractions, CNH points, vehicles by owner), but the platform-level tools overlap: authenticate/connect/toolkit_info all touch connection/auth status, and marketplace bundles many separate capabilities into one broad tool. This creates some boundary confusion for an agent selecting between them.
Naming Consistency2/5
Domain tools follow a consistent 'multas_' prefix pattern, but utility tools use inconsistent English verb/noun styles: authenticate, connect, marketplace, report_bug, show_version, toolkit_info. Mixing Portuguese noun-phrase names with generic English imperative/descriptive names makes the set feel disjointed and pattern-less.
Tool Count3/5
Eleven tools is within a reasonable range, but it feels top-heavy because only five tools actually serve the core fines-consulta domain while the rest are platform/account/admin utilities. The huge marketplace tool also compresses many sub-operations into one entry, making the count misleading.
Completeness4/5
The core query workflow is covered: find vehicles by owner, query vehicle debts by plate, check federal infractions, and verify CNH points. Missing features like fine payment or appeal detail are beyond the stated consulta purpose, so there are only minor workaround-level gaps for the apparent scope.