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 | [] |
Monte Bravo 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 provide idempotentHint=true; description adds reproduction context but no other behavioral traits beyond write intent. Does not contradict 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?
Two sentences, no wasted words, first sentence states purpose, second provides guideline.
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?
No output schema; description lacks return value explanation and full parameter guidance. Adequate for a simple feedback tool but not complete.
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?
With 0% schema description coverage, description only clarifies 'conversation' parameter purpose but not 'message' (required) or 'context'. Insufficient for 3 parameters.
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?
Description clearly states the tool reports bugs, missing features, or feedback, distinguishing it from sibling tools focused on Open Finance 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?
Explicitly advises including the conversation array for reproduction, though does not specify when to use vs alternatives, which are absent.
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
A3.9/5.0
Disambiguation3/5
Most openfinance_* tools target distinct resource/action pairs, but openfinance_list_connections and openfinance_get_item_status overlap on connection status/reconnect URLs, and openfinance_list_transactions vs openfinance_list_transactions_by_item can be confused. The long descriptions reduce ambiguity, but selection risk remains.
Naming Consistency3/5
The openfinance_* block is consistently verb_noun, but the platform tools mix bare verbs (authenticate, connect), nouns (marketplace), and noun_info (toolkit_info). No single naming convention spans the whole set, though each subgroup is internally readable.
Tool Count3/5
At 25 tools, this sits at the top of the heavy borderline range. The broad scope—MCP.AI platform management, prompt library, and Open Finance data—justifies many tools, but the set feels like a bundled suite rather than a tightly scoped single-purpose server.
Completeness4/5
The Open Finance side is well covered: accounts, balances, transactions, credit card bills, loans, investments, connections, sync, status, provider health, and category updates. The platform side has auth, toolkit info, marketplace, and feedback. Minor gaps exist, such as no explicit identity fetch or payment initiation, but those seem outside the intended read/analysis domain.