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 | [] |
Cadastro PJ Plus
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 already declare idempotentHint=true and destructiveHint=false. The description adds useful context that this is a feedback mechanism and that the conversation array aids reproduction. No contradiction with 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 sentence that front-loads purpose and includes a necessary usage hint. Every word earns its place.
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 has no output schema, but the description omits details about the conversation format (JSON string?), the meaning of context, and expected side effects. It's adequate for basic invocation but leaves gaps.
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?
Schema description coverage is 0%, so the description must compensate. It only mentions the conversation array, and even that is imprecise—the schema defines conversation as a string not an array. The required message and optional context parameters are not explained at all.
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 'Report' with clear objects: bug, missing feature, or feedback. This clearly distinguishes from sibling tools like authenticate, show_version, etc., which serve different purposes.
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 (when there is a bug, missing feature, or feedback) and provides an explicit instruction to include the conversation array for reproduction. While it doesn't name alternatives or exclusions, the tool is unique among siblings, making the context clear.
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
Most tools are distinct in purpose, but there is some overlap between authenticate, connect, and marketplace—especially since marketplace's invoke can return connection links. The single domain-specific tool (cnpj_cadastral_plus_consultar) is clearly separate from the platform utilities.
Naming Consistency2/5
Naming is inconsistent: it mixes English and Portuguese, verb-only (authenticate, connect), noun-only (marketplace), and snake_case verb_noun (report_bug, show_version) with no coherent pattern. The Portuguese tool name cnpj_cadastral_plus_consultar follows a different convention entirely.
Tool Count2/5
With 7 tools, the count is reasonable, but only one actually relates to the server's apparent domain (CNPJ data). The remaining six are generic platform utilities (marketplace, connect, toolkit_info, etc.) that don't belong in a specialized server and dilute its focus.
Completeness2/5
The CNPJ domain is severely underrepresented: there is only a single query tool and no other operations such as validation, list, or update. The generic platform tools do not fill these gaps, making the set incomplete for its stated purpose.