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 | [] |
CPFL: Download via link
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true) and the description adds behavioral context: requiring conversation array for reproduction. No contradiction; description complements 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?
Two sentences, front-loaded with purpose and a single critical instruction. No fluff, every word earns its place.
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?
For a simple bug-report tool with 3 params and no output schema, the description covers the core function and reproduction guidance but leaves parameter semantics incomplete (especially 'context' and message format). Acceptable minimum but not thorough.
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%, so the description must explain parameters. It only mentions the conversation array, omitting 'context' and 'message' (the required one). The string-encoded format of conversation is not clarified, and context is 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 uses a specific verb 'report' with clear resources: bug, missing feature, or feedback. It clearly distinguishes from siblings (authenticate, connect, marketplace, etc.) which are unrelated.
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?
Provides clear context: for reporting issues/feedback, and explicitly instructs to include the conversation array. Does not explicitly exclude other tools, but given sibling purposes, the intended use is unambiguous.
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.3/5.0
Disambiguation2/5
Multiple tools have fuzzy boundaries: `connect` and `toolkit_info` both report connection status; `authenticate` overlaps with `connect`'s URL/token flows; and the hardcoded `contas_cpfl_link_consultar` duplicates the marketplace's stated ability to 'consulta um CPF'. The platform-info cluster (connect/show_version/toolkit_info) would leave an agent guessing which one answers 'what's the current state'. Only `report_bug` feels clearly separated.
Naming Consistency2/5
Naming mixes bare imperative verbs (connect, authenticate, marketplace) with snake_case compound verbs (report_bug, show_version) and a noun-phrase (toolkit_info). The Brazilian tool `contas_cpfl_link_consultar` breaks the pattern entirely, using Portuguese noun-verb order. No coherent convention unifies the set.
Tool Count3/5
At seven tools, the raw count is within the reasonable 3–15 range and suits a platform-scoped server. However, the `marketplace` tool is a monolith bundling a dozen sub-operations (search, invoke, install, subscribe, prompt library), making the effective surface imbalanced. The marginal report_bug/show_version utilities feel tacked on next to that god-tool.
Completeness3/5
The platform loop is mostly covered: authenticate, connect, discover/invoke/install via marketplace, and report_bug for feedback. However, the server's namesake domain ('CPFL: Download via link') is represented by a single hardcoded tool with no sibling operations, and billing/account management for the paid per-query flow is relegated inside `marketplace`. It works end-to-end but leaves the strongest domain concern shallow.