Skip to main content
Glama

compatsy home espresso

Report a data issue

report_issue

Flag a wrong spec, price or fit verdict. Reports never edit facts; two independent reports mark a fact disputed. Example: {"entity_type":"product","entity_id":"breville-barista-express","field":"portafilter_mm","claim":"Breville lists a 54 mm portafilter for the Barista Express"}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>",
      "claim": "<claim>"
    },
    "name": "report_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes
fieldNo
entity_idYes
entity_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds context beyond annotations that matter: reports never edit facts, and two independent reports are required before a fact becomes disputed, which explains the non-idempotent, non-destructive write. It does not say whether a response is returned, whether a reporter can submit twice, or what happens during review.

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?

Three short front-loaded sentences: what to flag, the key non-obvious rule, then a worked example. Nothing is padding, and the example earns its space by encoding parameter formats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter write tool with no output schema, the definition covers the effect (no fact mutation) and consequence (disputed after two reports). It stops short of describing the acknowledgement returned or any abuse/rate constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the example carries the load, and it effectively demonstrates all four fields including the field-naming style ("portafilter_mm") and claim phrasing. Gaps remain for the offer/fit enum branches and for when field is legitimately omitted.

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?

"Flag a wrong spec, price or fit verdict" gives a specific verb and enumerates the exact resource classes it covers, which an agent can map to the catalog siblings. It does not name any sibling explicitly, but the write-vs-read split from get_product/search_products is unmistakable.

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 trigger condition is clear: use this when a spec, price, or fit verdict is wrong. What is missing is the when-not side, e.g. verify with get_product/check_fit first, or the boundary for missing data versus incorrect data.

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.