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 | [] |
BV 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 already indicate readOnlyHint=false and destructiveHint=false, so the agent knows it's a write operation but not destructive. The description adds that the conversation array should be included for reproduction, which is useful but doesn't significantly expand beyond 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?
The description is two sentences, front-loads the purpose, and contains no superfluous words. Every sentence provides essential information.
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?
Given the simplicity of the tool (3 parameters, no output schema, no nested objects), the description is largely complete. It covers the main action and key parameter guidance, though it could optionally mention what happens after a report is submitted.
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 description coverage is 0%, so the description must compensate. It explains the 'conversation' parameter ('include the conversation array with recent messages'), but 'message' and 'context' are not described. This provides partial but incomplete parameter information.
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 action 'Report' and the resources 'bug, missing feature, or send feedback', distinguishing it from the sibling tools which are primarily Open Finance operations. The verb and resource are specific and unambiguous.
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 implies usage for reporting issues or feedback but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not-to-use guidance is provided.
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/5.0
Disambiguation3/5
The openfinance_* tools are mostly distinct resource/action pairs, but several boundaries blur: openfinance_list_transactions vs openfinance_list_transactions_by_item vs openfinance_get_credit_card_bill(include_transactions) all return transaction data, and openfinance_get_item_status / openfinance_provider_status / openfinance_list_connections all concern connection health. The monolithic marketplace tool also bundles search/describe/invoke/install/prompt-library operations, adding further ambiguity.
Naming Consistency4/5
The 19 openfinance_* tools follow a clean snake_case verb_noun pattern (list_accounts, get_item_status, update_transaction_category), but the six platform tools break it with bare verbs (authenticate, connect) and noun-style names (marketplace, toolkit_info). The split is namespace-based and still readable, so it is only a minor inconsistency.
Tool Count3/5
25 tools is on the heavy side, but the server spans two domains: an Open Finance banking surface (accounts, bills, loans, investments, connections) and a marketplace/platform layer (auth, search, prompts, bug reporting). Many openfinance tools are necessary for that breadth, though the count is high enough to feel bloated.
Completeness4/5
The Open Finance surface is nearly complete: connections can be searched, listed, disconnected, force-synced, and health-checked; accounts, transactions, bills, loans, and investments all have read/detail paths; transaction categories can be updated. Minor gaps exist, such as no granular marketplace tools outside the monolithic marketplace tool and no single-transaction detail endpoint, but core workflows do not dead-end.