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 | [] |
Conselho Federal de Farmácia: Cadastro
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover idempotency (idempotentHint=true) and non-destructiveness (destructiveHint=false), so the description need not repeat those. It adds the useful behavioral detail that the conversation array should be included for reproduction. However, it does not disclose what happens after reporting, any external side effects, or whether a confirmation is returned.
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 short sentences with no filler. It front-loads the purpose and immediately provides the key usage instruction about the conversation array.
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 feedback/reporting tool with three string parameters and no output schema, the description covers the core behavior and the most important parameter. It could be more complete by clarifying what should go in 'message' and 'context', but overall it is sufficient for basic invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/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 does add meaning for the 'conversation' parameter by explaining it should contain recent messages for reproduction. However, it does not clarify the semantics of 'message' (the required parameter) or 'context', leaving two of three parameters under-described.
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 verb and resource: 'Report a bug, missing feature, or send feedback.' This is specific and differentiates it from sibling tools like authenticate, connect, and show_version, which serve unrelated 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 gives clear context for when to use the tool: whenever the user wants to report a bug, missing feature, or provide feedback. It does not explicitly name alternatives or exclusions, but the sibling tools are distinct enough that the intended usage is 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
B3.3/5.0
Disambiguation4/5
Most tools have clearly distinct purposes: authenticate handles auth token, connect reports connection status, marketplace manages MCP catalog operations, and cff_cadastro_consultar is the only domain query tool. However, connect and toolkit_info overlap in reporting connection status, and marketplace's many internal actions (search, describe, invoke) could cause ambiguity with toolkit_info's list of installed MCPs.
Naming Consistency2/5
Naming is inconsistent: some tools use plain verbs (authenticate, connect, report_bug), some use noun-style (marketplace, toolkit_info), and the domain tool cff_cadastro_consultar uses a different underscore-separated pattern. No coherent verb_noun or noun_verb convention is followed.
Tool Count3/5
Seven tools is a moderate count, but for a server named 'Conselho Federal de Farmácia: Cadastro' only one tool is domain-specific. The remaining six are generic platform utilities, making the set feel under-scoped for the apparent purpose and heavily weighted toward infrastructure rather than the core domain.
Completeness2/5
The domain surface is severely incomplete: cff_cadastro_consultar provides only a single consultation operation, with no update, list, or administrative tools. While platform utilities (marketplace, authenticate, etc.) are comprehensive, they do not address the stated purpose of cadastro queries, leaving agents with a dead end for any non-consultation need.