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 | [] |
Méliuz MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide idempotentHint=true and destructiveHint=false. The description adds that the conversation array should be included for reproduction, but does not elaborate on other behaviors like side effects or response.
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 concise sentences: first states the purpose, second gives a crucial usage instruction. No wasted words, effectively front-loaded.
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 no output schema and simple parameters, the description covers the essential use case. It could mention what happens after submission or expected outcomes, but the tool seems straightforward.
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 adds meaning for the 'conversation' parameter (include recent messages), but does not explain 'message' or 'context' beyond their names.
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 is for reporting bugs, missing features, or sending feedback. This distinguishes it from all sibling tools which focus on open finance operations or authentication.
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?
The description specifies when to use the tool (to report bugs, missing features, or feedback). It implicitly differentiates from siblings, but lacks explicit 'when not to use' or alternative tools.
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.2/5.0
Disambiguation5/5
Each tool targets a distinct operation or data type (accounts, transactions, bills, loans, investments, connections, etc.) with no ambiguity. Even closely related tools like openfinance_list_transactions and openfinance_list_transactions_by_item are clearly differentiated by scope and output format.
Naming Consistency3/5
The majority of tools follow the 'openfinance_' prefix for banking operations, but utility tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break this pattern, creating an inconsistent mix. However, the convention is still readable and the utilities are clearly distinct.
Tool Count4/5
25 tools is on the high side but well-justified by the breadth of Open Finance data types (accounts, transactions, credit cards, bills, loans, investments) and supporting operations (sync, status, search, updates). A few tools could potentially be merged, but overall the number is reasonable for the domain.
Completeness4/5
The tool surface covers the core Open Finance workflows: listing, reading details, syncing, updating categories, and checking provider status. Minor gaps exist (e.g., no tool to create or delete accounts/transactions), but these are external constraints. The set enables most user-facing financial queries and actions.