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 | [] |
Carrefour MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds behavioral context beyond annotations: conversation array needed for reproduction. Annotations note idempotentHint=true (no contradiction). No destructive behavior mentioned, which aligns with destructiveHint=false.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no fluff. Could be more structured but efficient for the purpose.
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?
Simple reporting tool with no output schema. Description covers main usage but lacks parameter details. Adequate for basic invocation.
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 description must explain parameters. It only describes the 'conversation' parameter, leaving 'context' and 'message' unexplained. Message is required but no semantics provided.
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, using specific verb and resource. It distinguishes from siblings which are all finance-related.
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 says to include the conversation array for reproduction, guiding when to use. Does not mention exclusions or alternatives, but context signals indicate this is the only bug-reporting tool.
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 openfinance_* cluster maps cleanly to distinct resources/actions and the descriptions sharply separate lookalikes like openfinance_get_item_status vs openfinance_provider_status. A few boundaries are fuzzy: openfinance_list_transactions_by_item overlaps with openfinance_list_transactions, marketplace also exposes report_bug alongside the standalone report_bug tool, and get_account_balance/list_accounts both return balances.
Naming Consistency4/5
The 20 finance tools consistently follow openfinance_<verb>_<noun> (list_accounts, get_credit_card_bill, force_sync, update_transaction_category), which is the dominant pattern. The five platform tools break it with bare verbs and nouns (connect, marketplace, toolkit_info, show_version), creating a clear but minor namespace split.
Tool Count4/5
25 tools is at the heavy end of the typical range, but the server covers two substantial domains (Open Finance data and an MCP marketplace/platform), so most tools earn their place. There is little redundant surface; the only mild overreach is marketplace smuggling many sub-operations into one tool.
Completeness4/5
The Open Finance surface is remarkably complete: accounts, balances, transactions, credit card bills, loans, investments, categories, connection health, force sync, connector search, and disconnect. Minor gaps remain, such as no direct programmatic bank-connection creation tool (URLs are returned instead) and no singular transaction/get-investment-detail endpoint, but agents can work around these.