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 | [] |
Sicredi MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate idempotentHint=true and destructiveHint=false, reducing the burden. The description adds value by specifying that conversation data aids reproduction, which is a behavioral hint beyond annotations. No contradictions.
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 filler. Every sentence adds value: purpose and a concrete usage instruction. Perfectly concise for the tool's simplicity.
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?
While annotations cover safety and idempotency, the description lacks detail about the required 'message' parameter (what content to provide) and 'context'. For a 3-param tool with no output schema, the description should explain all inputs more fully.
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 for reproduction) but leaves 'message' (required) and 'context' undescribed. Partial coverage, adequate but not thorough.
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 reports bugs, missing features, or sends feedback. This verb+resource combination is specific and distinct from sibling tools (e.g., openfinance, authenticate), which focus on financial data or system functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says when to use the tool (report bug, missing feature, or feedback) and provides a concrete guideline: include the conversation array with recent messages for reproduction. No alternative tools exist for this purpose among siblings.
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 have clearly distinct resource-action pairs, but several pairs overlap enough to cause misselection: authenticate vs connect, openfinance_list_accounts vs openfinance_get_accounts_detail, and openfinance_list_credit_card_bills vs openfinance_get_credit_card_bill. The long descriptions help, but the monolithic marketplace tool also mixes many sub-actions that overlap with report_bug and connection management.
Naming Consistency3/5
The openfinance_* tools mostly follow a consistent openfinance_<verb>_<noun> pattern, and the utility tools are all snake_case, but the conventions are mixed: marketplace is a bare noun, connect/authenticate are bare verbs, and openfinance_provider_status/toolkit_info lack a verb prefix. The pattern is readable but not uniform across the whole set.
Tool Count3/5
At 25 tools, this sits at the top of the borderline-heavy range. The Open Finance domain justifies many of them, but the marketplace mega-tool plus several overlapping list/get variants make the set feel larger than necessary.
Completeness4/5
The surface covers the full Open Finance lifecycle well: connection search/status/sync/disconnect, accounts, balances, transactions, credit card bills, loans, investments, and category correction. Minor gaps exist, such as no direct payment/transfer initiation or single-transaction detail endpoint, but these are outside the apparent read/aggregate purpose and are workable around.