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 | [] |
QI SCD 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 indicate idempotentHint=true and destructiveHint=false. The description adds that the tool accepts a message and conversation for feedback but does not disclose any behavioral aspects beyond what annotations provide, such as how the feedback is processed.
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, each serving a purpose: first states the overall function, second provides actionable guidance. It is front-loaded and free of unnecessary words.
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 tool's simplicity (3 parameters, no output schema), the description covers the essential use case and provides guidance on reproduction. It could mention that feedback is sent to developers, but it is largely complete.
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 recent messages) but does not explain context or message in detail. This partially covers the parameters but leaves the context parameter ambiguous.
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. It specifies the verb 'report' and resource types, and distinguishes itself from sibling tools which are all finance-related or authentication 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?
The description advises including the conversation array for reproduction, which gives clear usage guidance. While it doesn't explicitly state when not to use this tool, the sibling tools are all unrelated, so context is adequate.
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
Disambiguation4/5
Most tools are clearly distinct, especially within the openfinance_* group, with detailed descriptions covering specific resources and actions. Minor overlap exists between list_transactions and list_transactions_by_item, and between get_credit_card_bill and list_credit_card_bills, but the descriptions clearly delineate their use cases (per-account vs whole-connection, detail vs summary).
Naming Consistency4/5
The openfinance_* tools consistently follow a verb_noun pattern (e.g., list_accounts, get_item_status, update_transaction_category), with the exception of openfinance_provider_status which uses a noun phrase. Non-openfinance tools like authenticate, connect, marketplace, and report_bug are less uniform but still readable. Overall, the convention is mostly consistent.
Tool Count4/5
At 25 tools, this is on the higher end but justified by the comprehensive Open Finance domain covering accounts, transactions, credit cards, loans, investments, connections, categories, and provider status. Each tool serves a specific operation, and the marketplace and platform utilities round out the surface. It's slightly heavy but not excessive.
Completeness5/5
The tool surface covers the full lifecycle for Open Finance data: listing and detailing accounts, retrieving balances, managing transactions (including categorization), handling credit card bills (list and detail with transactions), loans, investments, and connection health (sync, status, disconnect, search). Also includes authentication, marketplace, and utility tools. No obvious gaps for the stated purpose.