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 | [] |
Bradesco MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate idempotentHint true and no destructiveness, aligning with the description. However, the description adds little beyond stating the purpose, missing details like whether it creates a ticket or logs data.
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 with no waste, front-loaded with purpose, and each sentence adds value.
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?
Simple tool with no output schema, but parameters are under-described. The description is adequate for a basic feedback tool but could elaborate on what happens after reporting.
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 coverage is 0%, and the description only mentions the conversation parameter, ignoring context and message. The required message parameter lacks any explanation of its content or format.
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 reports bugs, missing features, or feedback, which is specific and distinguishes it from sibling tools focused on openfinance operations.
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 advises including the conversation array for reproduction, giving context for use. While not specifying when not to use it, the purpose is clear enough to guide selection.
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.9/5.0
Disambiguation3/5
The openfinance_* tools are mostly separated by resource and verb, but there are several borderline pairs: list_transactions vs list_transactions_by_item, get_item_status vs list_connections vs provider_status, and list_accounts vs get_account_balance. The marketplace tool also bundles search/describe/invoke/install/report_bug/prompt-library actions, which overlaps with standalone report_bug and adds confusion.
Naming Consistency3/5
The openfinance_* family follows a clean get_/ list_/ update_ pattern, but the platform tools mix bare verbs like connect and authenticate with noun-style names like marketplace and toolkit_info. This split is readable but not a single consistent convention.
Tool Count3/5
25 tools sits at the upper end of the 16-25 'heavy' band. The Open Finance domain genuinely has many resources and the openfinance_* tools mostly earn their place, but the generic platform tools plus the multi-purpose marketplace make the set feel larger than its core purpose requires.
Completeness4/5
The Open Finance lifecycle is well covered: connection search/link/status/sync/disconnect, accounts/balances/detail, transactions with categorization, credit-card bills with derived payment status, loans, and investments with transaction history. Minor gaps exist, such as no standalone connect/install tools, but those flows are handled via URLs and embedded marketplace actions rather than missing entirely.