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 | [] |
Tiny (Olist Tiny)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not elaborate on side effects, idempotency, or safety beyond the annotations. It implies a reporting action but doesn't explain consequences or if repeated calls are problematic. Annotations cover some aspects, but the description adds minimal transparency.
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 a single sentence, concise and to the point. It avoids unnecessary verbosity while conveying the core purpose and a usage hint.
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 details about expected input formats, the role of 'context', and any output or confirmation. It does not fully clarify what constitutes a valid report, leaving the agent with gaps in understanding.
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 'conversation array' but the parameter is a string, causing ambiguity. It does not explain the 'context' parameter at all, and omits format or expected content for 'message'. Schema coverage is low.
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 specifies the action (report) and the resource (bug/feature/feedback), making it distinct from sibling tools.
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?
It provides a hint to include the conversation array, but lacks explicit guidance on when to use this tool versus alternatives. No mention of prerequisites or situations that warrant its use.
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.1/5.0
Disambiguation2/5
The tiny_* tools are clearly distinct by resource and action, but the generic platform tools blur together: marketplace also handles report_bug, install/uninstall, token/connect links, and toolkit state, overlapping with authenticate, connect, report_bug, and toolkit_info. An agent could easily call marketplace for something a dedicated tool already covers, or confuse connect with authenticate.
Naming Consistency3/5
The Tiny ERP tools follow a clean verb_noun pattern (tiny_list_orders, tiny_get_product, tiny_create_contact), but the platform tools use short unprefixed verbs (authenticate, connect, marketplace, report_bug, show_version, toolkit_info). Two internally consistent naming schemes coexist, so the overall set feels mixed rather than chaotic.
Tool Count3/5
At 20 tools, the count is borderline heavy and mixes two distinct concerns: Tiny ERP operations and mcp.ai platform administration. The ERP tools are each reasonably scoped, but the generic tools could likely be consolidated, especially marketplace, which already absorbs several capabilities.
Completeness2/5
The ERP surface is heavily read-oriented: contacts, orders, invoices, products, payables, and receivables all support list/get, but only contacts have a create operation. There are no update/delete operations for any entity and no way to create orders, invoices, or products, which creates significant dead ends for real business workflows.