report_bug
Idempotent
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | ||
| message | Yes | ||
| conversation | No | [] |
DETRAN PI: Multas
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds that the conversation array should be included for reproduction, giving some behavioral context. It does not contradict annotations and provides minimal but adequate transparency for a submission tool.
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 two concise sentences with no redundant information. It directly states the purpose and provides a specific instruction, making it well-structured and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the description captures the core action, but it lacks details on what message should contain, what context means, or what the return value is (no output schema). This leaves some gaps for a fully self-contained description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides no parameter descriptions (0% coverage). The description only hints at the 'conversation' parameter ('Include the conversation array with recent messages') but does not explain the 'message' or 'context' fields. This leaves most parameter semantics unclear.
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's purpose: 'Report a bug, missing feature, or send feedback.' It uses specific verbs and a clear object, distinguishing it from sibling tools like authenticate or connect.
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 the tool (when reporting bugs, missing features, or providing feedback) and provides a usage hint ('Include the conversation array'). It does not explicitly mention alternatives, but the sibling context makes the use case obvious.
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
Disambiguation5/5
Each tool has a clearly distinct purpose: authentication, connection, marketplace operations, bug reporting, version display, toolkit state, and the single DETRAN query. No two tools overlap in function, so an agent can easily tell them apart.
Naming Consistency3/5
All names use snake_case and are lowercase, but the pattern is inconsistent: sometimes verb-only (authenticate, connect), sometimes verb+noun (show_version, report_bug), sometimes noun+verb (detran_pi_multas_consultar), and sometimes noun-only (marketplace, toolkit_info). There's no consistent verb_noun pattern across the set.
Tool Count2/5
7 tools is within the typical range, but the majority are generic platform utilities (authenticate, marketplace, etc.) unrelated to the server's stated purpose (DETRAN PI fines). Only one domain-specific tool exists, so the count is not well-aligned with the apparent scope.
Completeness2/5
The only domain tool is detran_pi_multas_consultar, which handles a single query operation. There are no other fine-related operations (e.g., list, payment, history), so for the declared purpose the coverage is minimal. The additional platform tools don't address the domain.