Skip to main content
Glama

compatsy 3D printing

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":"prusa-mk4s","field":"nozzle_thread","claim":"MK4S uses the Nextruder thread"}

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

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false; the description adds genuinely new behavior: reports never mutate facts, and two independent reports are needed before a fact is marked disputed. That explains the non-idempotent flag meaningfully. It omits any mention of auth/rate limits or what the caller receives back, keeping it below 5.

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 tight sentences: purpose, behavioral rule, then a worked example. Front-loaded and every clause carries information an agent needs; no filler.

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 4-parameter flag tool with no output schema, the definition covers intent, the dispute mechanism, and a usable example payload. The main remaining gap is what a successful call returns and whether repeat reports from the same caller count toward the two-report threshold.

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?

With 0% schema description coverage, the description compensates well by giving a concrete example payload that shows entity_id as a slug ('prusa-mk4s') and field as a specific attribute ('nozzle_thread'), plus the free-text nature of claim. It leaves the valid values for 'field' and the meaning of the offer/fit entity types implicit.

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?

Opens with a specific verb and object set: 'Flag a wrong spec, price or fit verdict.' An agent can immediately distinguish this write/flag action from the read-oriented siblings (get_product, search_products, check_fit, check_stock, compare) without inspecting schemas.

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?

States the triggering condition clearly (wrong spec, price or fit verdict) and adds the important constraint that reporting does not itself edit data, which implicitly routes correction intent here rather than to an edit tool. It does not explicitly name an alternative tool or a when-not-to-use case, so it stops short of a 5.

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.