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 | [] |
Conta Simples
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 adds minimal behavioral context beyond 'report' which implies submission. Annotations give idempotentHint true, but reporting is typically non-idempotent; the description does not clarify this discrepancy or disclose effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (one sentence), but at the cost of omitting essential parameter details; it is succinct but incomplete.
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 tool has 3 parameters and no output schema; the description fails to fully document all parameters or specify outcomes, making it inadequate for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/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, leaving 'message' (required) and 'context' 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?
Description clearly states the tool reports bugs, missing features, or feedback. It is distinct from sibling tools that focus on contasimples operations or general utilities.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives some usage guidance by requesting the conversation array for reproduction, but does not explicitly state when to use or avoid this tool compared to siblings.
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.5/5.0
Disambiguation4/5
Almost all tools have clear purposes, especially with the contasimples_ prefix. Some overlap between statement and summary, but descriptions differentiate well. The general tools (marketplace, report_bug, etc.) are completely different from the financial ones, which reduces potential confusion.
Naming Consistency3/5
The domain tools follow a consistent verb_noun pattern (e.g., contasimples_card_write_block). However, the inclusion of general tools like authenticate, connect, marketplace breaks the pattern. This inconsistency lowers the score.
Tool Count4/5
With 24 tools covering authentication, financial operations, and platform utilities, the number is reasonable for a moderately complex MCP server. It doesn't feel excessive or too thin.
Completeness3/5
The toolset covers key financial operations (balance, bills, cards, statements, summary) and some mutations (block/unblock, create invite, delete user). However, missing CRUD for several entities (e.g., no update user, no create card, no delete invite) leaves gaps. The presence of platform utilities adds breadth but not depth.