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 | [] |
Mercos
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any behavioral side effects beyond what annotations already state. It doesn't mention whether data is transmitted, stored, or how it is processed, leaving the user unaware of the tool's impact.
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 extremely concise, using a single sentence to convey the key action and a specific instruction. There is no redundancy or unnecessary wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks sufficient context about how to use the tool effectively. It does not explain what constitutes a valid bug report, how to format the conversation array, or what the 'context' field is for, making the tool under-specified.
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?
The description mentions the 'conversation array' but does not clarify the meaning or required format of 'context' or 'message'. Since the schema provides no descriptions, this leaves two parameters completely unexplained.
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: reporting bugs, missing features, or sending feedback. It is specific and unambiguous, leaving no doubt about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus other tools or when not to use it. It lacks contextual triggers or alternative recommendations, providing only a generic 'report' instruction.
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
Disambiguation4/5
The Mercos tools are clearly separated by resource type (clientes, pedidos, produtos, etc.) with consistent list/create/update patterns. The only potential confusion is between the platform-level tools (authenticate, connect, marketplace, toolkit_info) and the Mercos-specific tools, but their descriptions are distinct enough. The marketplace tool is overloaded with many sub-actions (search, describe, invoke, install, subscribe, etc.) which could be ambiguous, but it's a single tool with a clear purpose.
Naming Consistency4/5
Mercos-specific tools follow a consistent pattern: mercos_<verb>_<resource> (e.g., mercos_list_clientes, mercos_create_pedido, mercos_update_produto). Platform tools use simple verbs (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) which are consistent in style but not following the same verb_noun pattern. The naming is mostly predictable, with minor deviation for platform tools.
Tool Count4/5
25 tools is on the higher end but still reasonable for a server that combines a platform toolkit (marketplace, auth, etc.) with a full ERP integration (Mercos). The Mercos tools cover 8 resources with list/create/update where applicable, which justifies the count. It's slightly heavy but each tool has a clear purpose.
Completeness4/5
The Mercos integration covers the main CRUD operations for core entities (clientes, pedidos, produtos, tabelas_preco) with list, create, and update. Missing delete operations for most resources, and some resources only have list (categorias, comissoes, condicoes_pagamento, titulos, transportadoras, usuarios) which is fine for reference data. The platform side is comprehensive with marketplace, auth, and toolkit management. Minor gaps like no delete for Mercos entities, but agents can work around.