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 | [] |
SINTEGRA: MA
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 indicate the tool is idempotent and non-destructive. The description adds minimal behavioral detail, only mentioning the need to include conversation for reproduction. It does not elaborate on side effects or prerequisites, but it does not contradict the 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, concise sentence that conveys the essential information without extraneous details. It efficiently captures the tool's purpose and key usage instruction.
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?
The description adequately covers the tool's main function and the key input requirement (conversation). It does not discuss output or errors, but no output schema exists, so that is not a gap. Overall, it provides sufficient context for typical use.
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?
The description explains the purpose of the 'conversation' parameter ('recent messages for reproduction') but does not clarify 'context' or 'message'. With only partial coverage of three parameters, the description adds some value but leaves other parameters unspecified.
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 distinguishes itself from sibling tools like 'authenticate' and 'show_version' by focusing on issue reporting.
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 provides implicit guidance on when to use the tool (when reporting a bug or providing feedback) and explicitly instructs to include the conversation array for reproduction. It does not explicitly mention alternatives, but the purpose is clear enough.
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.4/5.0
Disambiguation2/5
The marketplace tool is a mega-tool containing search, describe, invoke, install, subscribe, prompt-library, and even bug-reporting actions, which overlaps with the separate report_bug tool. connect and toolkit_info also overlap in connection/status reporting, making tool selection ambiguous.
Naming Consistency2/5
Names mix verb-style actions (authenticate, connect, report_bug), noun-style labels (marketplace, toolkit_info), and an inconsistent Portuguese snake_case domain tool (sintegra_ma_consultar). There is no clear or predictable naming convention across the set.
Tool Count3/5
Seven tools is a reasonable count, but it is misleading because marketplace alone bundles well over ten distinct capabilities under one name. The surface would be more coherent and better counted if those actions were split out.
Completeness3/5
The server covers authentication, connection status, marketplace discovery/execution/install, bug reporting, version info, and toolkit state. However, management operations like uninstall/subscription handling are hidden inside marketplace, and the SINTEGRA MA domain is reduced to a single query with no related history or supporting tools.