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 | [] |
Asaas
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds no further behavioral context (e.g., who receives the report, side effects). It does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the purpose. It is concise, but could be slightly more structured by explaining parameter roles.
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?
No output schema exists, and parameters are partially described. For a simple feedback tool, the description covers the basics but leaves ambiguity about required inputs and expected outcomes.
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%. The description only mentions the conversation parameter but fails to explain the required 'message' parameter or the optional 'context' parameter. Without parameter descriptions, the agent cannot determine how to fill these fields.
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 reports bugs, missing features, or feedback. The verb 'report' and resource 'bug/feedback' are specific, and the tool is distinct from siblings which are for authentication, discovery, etc.
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 explicitly advises to include the conversation array for reproduction, which is a helpful usage tip. However, it does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives, as no direct sibling exists.
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.7/5.0
Disambiguation3/5
Tools have distinct primary purposes, but marketplace and search_tools overlap heavily: both cover search/describe/invoke for the MCP catalog. An agent may be uncertain which to call for a simple catalog lookup, though marketplace's broader scope (install, prompts, billing) helps differentiate.
Naming Consistency3/5
Most tools use verb_noun style (report_bug, search_tools, show_version) or bare verbs (authenticate, connect), but 'marketplace' and 'toolkit_info' are noun-based. The mixed conventions are still readable and predictable enough.
Tool Count5/5
Seven tools is well-scoped for a platform management server. Each tool covers a distinct area: auth, connection status, catalog access, feedback, version, and toolkit state, with no bloat.
Completeness4/5
The surface covers core platform operations: authentication, connection checks, catalog search/invoke (via marketplace and search_tools), bug reporting, version info, and toolkit state. Minor gaps like explicit uninstall or user management are handled indirectly through marketplace's install/subscribe actions.