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 | [] |
Uber Conta by Digio MCP
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-destructive and idempotent. The description adds the requirement to include the conversation array, which gives useful behavioral context for how the tool should be invoked.
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 concise and front-loaded, using two short sentences to convey purpose and usage without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 3-param tool with no output schema, the description adequately covers the essential details, though it doesn't explain the response or all parameter semantics.
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 coverage is 0%, but the description clarifies the `conversation` parameter and implies `message` is the report content. `context` remains undefined, but it has a default.
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 function: reporting bugs, missing features, or feedback. It uses specific verbs and is distinct from the sibling OpenFinance tools.
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 gives clear context that the tool is for reporting issues and specifies to include the conversation array for reproduction. No alternatives are mentioned, but none exist among 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
A4.3/5.0
Disambiguation4/5
The openfinance_* tools are mostly distinct list/get/update/sync operations, and the non-openfinance tools are clearly separate platform utilities. A few pairs could be confused, such as openfinance_list_accounts vs openfinance_get_accounts_detail, or openfinance_get_item_status vs openfinance_list_connections, but the descriptions generally make the intended use clear.
Naming Consistency4/5
The domain tools follow a consistent openfinance_verb_noun pattern, making the bulk of the API predictable. The deviation comes from the six non-prefixed platform tools, and one or two names like openfinance_provider_status are noun-led rather than verb-led, but overall the convention is coherent.
Tool Count3/5
25 tools is at the heavy end of the range, and the server would feel tighter if some get/list pairs were consolidated. However, the breadth is somewhat justified by the number of Open Finance resource types covered: accounts, transactions, bills, investments, loans, connections, categories, and sync/status operations plus platform utilities.
Completeness5/5
The Open Finance surface is thorough: connection lifecycle, account data, balances, transactions, credit card bills, investments, loans, categories, sync, and provider health are all covered. There are no significant dead ends, and the additional platform tools handle authentication, marketplace discovery, and system information.