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 | [] |
Next MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotent and non-destructive writes. The description adds that including conversation is needed for reproduction, which is helpful behavioral context but does not disclose if there are side effects, rate limits, or return behavior beyond that.
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 concise sentences with no wasted words. It is front-loaded with the core purpose and immediately provides an actionable tip.
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?
Given the tool's simplicity (reporting bug/feedback) and lack of output schema, the description is minimally complete. It tells the agent what to include but does not explain the return value or confirm submission, which could be useful.
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 has 3 parameters with 0% description coverage. The description only covers the 'conversation' parameter by mentioning it should be included for reproduction. The 'context' parameter is not explained, and 'message' is self-evident. This partially compensates but leaves gaps.
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 sending feedback. It identifies the resource and action, and is distinct from sibling tools which are unrelated to feedback. However, it could be more specific about the scope of 'feedback'.
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 advises including the conversation array for reproduction, which gives a usage hint. However, it does not provide explicit guidance on when to use this tool vs alternatives (though none exist among siblings), nor does it state any prerequisites or exclusions.
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.1/5.0
Disambiguation4/5
The tools are largely distinct, especially the openfinance_* suite which follows clear resource+action patterns. A few could be confused (e.g., openfinance_list_transactions vs openfinance_list_transactions_by_item, or get_account_balance vs list_accounts) but descriptions are thorough and clarify boundaries. The non-prefixed tools (authenticate, connect, marketplace) are also distinct, though 'marketplace' is quite overloaded internally.
Naming Consistency4/5
The openfinance_* tools follow a very consistent verb_noun pattern (list, get, force_sync, update, search, provider_status). However, the platform tools are heterogeneous: authenticate, connect, report_bug, show_version are verb_noun, but 'marketplace' and 'toolkit_info' are nouns. This mix is a minor inconsistency, but overall the naming is predictable across the two clear groups.
Tool Count4/5
At 25 tools, this is on the heavy side (16-25 is considered heavy), but the breadth is justified by a comprehensive Open Finance API (19 tools) plus platform management (6 tools). Each openfinance_* tool maps to a specific endpoint or operation, so none feel redundant. Slightly above the ideal 3-15 range, but appropriate for a full financial data adapter.
Completeness5/5
The Open Finance surface is remarkably complete: accounts, transactions, bills, loans, investments, categories, connection management (list, force_sync, status, provider_status, search connectors, disconnect), and even a categorization update. The platform side covers authentication, connectivity, marketplace operations (search/describe/invoke/install/subscribe), bug reporting, version, and toolkit info. No obvious dead ends or missing lifecycle steps.