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 | [] |
C6 Bank MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description advises including conversation data for reproduction, adding behavioral context beyond annotations. However, it doesn't disclose potential side effects or confirmation of submission. Annotations already mark it as idempotent and non-destructive.
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 essential usage instruction. No extraneous words.
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 3-parameter tool with no output schema, the description covers the main purpose and one key parameter. The 'context' parameter is left undocumented, slightly reducing completeness.
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?
With 0% schema parameter descriptions, the description partially compensates by explaining the 'conversation' parameter. 'message' is implied as the main content, but 'context' remains unexplained. Added value is moderate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool is for reporting bugs, missing features, or feedback, using specific verbs and resources. It distinguishes from siblings, none of which serve this purpose.
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?
No explicit when-to-use or alternatives are provided, but the purpose is implied by the tool name and description. Since no sibling tool overlaps, specific exclusions are less critical.
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 mostly target distinct resources, but several close pairs require careful reading: list_transactions vs list_transactions_by_item, get_item_status vs provider_status, and list_accounts vs get_accounts_detail. The oversized marketplace tool also embeds sub-actions like report_bug and list_tools that overlap with standalone tools, making boundaries less crisp.
Naming Consistency4/5
Names are predominantly lowercase snake_case with a strong openfinance_ prefix and clear verb_noun pairs such as list_accounts, get_account_balance, and update_transaction_category. A few platform-level tools break the pattern (marketplace, toolkit_info, authenticate, connect), but they are minor deviations and remain readable.
Tool Count3/5
At 25 tools, this is on the heavy end, and the server mixes a detailed Open Finance data adapter with platform-management tools like marketplace, authenticate, connect, and toolkit_info. The breadth is defensible for the domain, but the set feels overloaded and could reasonably be split or consolidated.
Completeness5/5
The Open Finance surface is unusually thorough: connection lifecycle, accounts, balances, transactions, cash-flow analysis, credit-card bills, investments, loans, categories, and provider status are all covered. List tools feed detail tools cleanly, and reconnect or force-sync paths exist for every staleness or authentication dead end.