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 | [] |
99Pay MCP
TDQS
A3.7/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 the reproduction hint but doesn't disclose what happens after reporting (e.g., ticket creation) or return behavior. With annotations covering safety, the description adds moderate value.
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 purpose, and a concise usage instruction. No wasted words; every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks information on expected input formats (e.g., JSON array for conversation), output/return value (no output schema), and error handling. For a 3-parameter tool, this is insufficient for full agent understanding.
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 coverage is 0%, so the description must compensate. It provides meaning for 'conversation' (include recent messages) but gives no detail about 'message' or 'context'. Only one of three parameters gets useful elaboration, leaving gaps.
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's purpose: reporting bugs, missing features, or sending feedback. The name 'report_bug' aligns, and it stands distinct from sibling tools (mostly openfinance_*).
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 provides a clear usage tip: 'Include the conversation array with recent messages for reproduction.' It implies when to use the tool but doesn't explicitly exclude alternatives or provide when-not-to-use guidance, though siblings are unrelated.
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.4/5.0
Disambiguation5/5
Each tool targets a distinct resource and action, with clear separation between general server utilities (authenticate, connect, marketplace) and the openfinance_* family (get/list/search/update per domain). No two tools appear to overlap: list_transactions vs list_transactions_by_item are differentiated by granularity, and get_item_status vs provider_status by scope. The marketplace tool, while broad, is explicitly named and described, so it doesn't cause ambiguity.
Naming Consistency5/5
All 20 openfinance_* tools follow a strict verb_noun snake_case pattern (list_accounts, get_account_balance, force_sync, update_transaction_category, etc.). The five general tools also use snake_case and clear names, maintaining consistency across the set. No mixing of conventions or inconsistent verb styles.
Tool Count4/5
At 25 tools, the set is on the higher end but well-justified for a platform that aggregates Open Finance data and provides a marketplace. The 20 openfinance tools cover distinct banking operations (accounts, transactions, bills, loans, investments, connections, sync, status, search, categories), each addressing a specific need. The 5 general tools handle authentication, connection status, and platform info. No obvious trivial or redundant tools; each earns its place.
Completeness5/5
The tool surface is comprehensive for the stated domain: CRUD-like coverage across financial resources (list/get for accounts, transactions, bills, loans, investments), plus state management (force_sync, disconnect, update_category) and ecosystem support (search_connectors, provider_status, marketplace). It also includes utilities like authenticate, connect, and version/bug reporting. No missing operations that would cause agent failures; the set covers connection lifecycle, data retrieval, and even API diagnostics.