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 | [] |
Antecedentes (Polícia Federal)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a non-read-only, non-destructive, and idempotent operation. The description adds useful context by instructing to include the conversation array for reproduction. However, it does not disclose post-submission behavior or side effects, leaving some transparency gaps.
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 conveys the core purpose and a key usage hint. No filler or repetition exists.
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?
Given the tool's simplicity, the description covers the main intent and the conversation field. However, it omits the 'context' parameter and any information about expected outcomes, making it adequate but not fully comprehensive.
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?
With 0% schema description coverage, the description must compensate. It adds meaning to the 'conversation' parameter by specifying it should contain recent messages, and implies 'message' is the report content. However, the 'context' parameter is entirely undocumented, leaving a semantic gap.
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 specific verbs ('Report', 'send') and identifies the resource ('bug, missing feature, or feedback'). This makes the tool's purpose immediately clear and distinguishable from the unrelated sibling tools.
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 implies usage for reporting issues but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The sibling tools are unrelated, but no context is given.
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 domain-specific tool is clearly distinct, but several platform tools overlap in scope: authenticate, connect, and toolkit_info all relate to connection/auth status, and marketplace is a multi-purpose tool that could be confused with the others. Overall boundaries are mostly clear due to detailed descriptions, but not perfectly distinct.
Naming Consistency2/5
Tool names are inconsistent: the domain tool uses a long snake_case phrase, while platform tools mix single nouns (authenticate, connect, marketplace) with underscored compounds (report_bug, show_version, toolkit_info). No clear naming convention is applied across the set.
Tool Count3/5
Seven tools is a reasonable number, but the composition is mismatched: only one tool relates to the server's stated domain (Antecedentes Polícia Federal), while the other six are generic MCP platform utilities. This makes the count feel padded for a domain-specific server.
Completeness4/5
For the core domain, the single consult tool fully covers the necessary query operation, and the infrastructure tools (auth, connect, marketplace) support the workflow. Minor gaps exist like batch queries or PDF export, but the surface is generally complete for its stated purpose.