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 | [] |
CRM
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-read-only, idempotent, and non-destructive behavior. The description adds a useful behavioral hint by instructing to include the conversation array for reproduction, but it does not explain side effects like sending data, authorization needs, or response behavior beyond what the annotations convey.
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, front-loaded with the core purpose, and includes only the essential operational instruction. No wasted words.
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, with no output schema and few parameters, but the description leaves the `context` parameter ambiguous and does not mention expected output or confirmation after reporting. It is minimally complete for basic invocation but has clear gaps.
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 carry the burden. It explicitly explains the `conversation` parameter's purpose and gives meaning to `message` through the main verb, but `context` is left unexplained. This is partial compensation, not full.
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, using a specific verb and resource. This distinguishes it from unrelated sibling tools like CRM operations or authentication.
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?
It provides clear context for when to use the tool: when a bug, missing feature, or feedback needs to be communicated. It does not explicitly mention alternatives, but none of the siblings perform this function, so the usage context is well implied.
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
Disambiguation4/5
The CRM tools are mostly distinct (CRUD, file operations, schema management), but there is potential confusion between crm_describe, crm_get_object, and crm_list_objects, and between crm_upload_file/crm_upload_from_url/crm_confirm_upload. However, descriptions clarify these somewhat. The set also includes auxiliary tools (authenticate, connect, marketplace, etc.) that are clearly separate.
Naming Consistency4/5
Most tools follow the crm_verb_noun pattern (crm_create_records, crm_delete_records, crm_update_records, etc.). Some deviations like authenticate, connect, toolkit_info, and show_version lack the crm_ prefix, and bulk support is noted in descriptions but not in names. Still, the convention is fairly consistent.
Tool Count3/5
With 36 tools, the count is on the heavier side. The CRM-specific tools (about 27) cover CRUD, schema, relationships, files, and usage, which is reasonable for a full CRM API. However, the inclusion of platform-level tools (marketplace, report_bug, show_version, toolkit_info) adds breadth that goes beyond CRM-specific functionality, making the set feel larger than necessary.
Completeness5/5
The tool surface is quite complete: full CRUD for records, objects, fields, files, relationships, search, and usage. The descriptions mention validations and bulk support, and the crm_describe tool prompts agents to understand schema first. Gaps are minimal—for instance, no explicit bulk delete for records but crm_delete_records supports bulk via ids. Overall, the domain is well-covered.