Skip to main content
Glama
Sign In

KH Merch Graph

by io.github.marleyhereicome-cpu
OverviewDiscussionsAdmin

Report a catalog mistake

report_correction

Report a mistake or missing item in the catalog (reviewed by hand before anything changes). Example: {sku_id: "ichiban-kuji-kh-2018-a", field: "msrp_jpy", proposed_value: "750", source_url: "https://…"}. Please include a primary source (maker, official shop or reliable press) when you can. Returns {accepted, correction_id}.

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": {
      "field": "<field>",
      "proposed_value": "<proposed_value>"
    },
    "name": "report_correction"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything else worth knowing. Optional.
fieldYesWhat is wrong, as a catalog field name, e.g. "name_en", "msrp_jpy", "availability_hint", "official", or "new_item".
sku_idNoThe item's sku_id. Leave empty to suggest a new item.
source_urlNoURL of a primary source that confirms it. Optional but strongly preferred.
proposed_valueYesThe correct value (or, for a new item, its name and details).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / field / description
      Previous value: -"修正したい列名（例: msrp_jpy, name_en）"New value: +"What is wrong, as a catalog field name, e.g. \"name_en\", \"msrp_jpy\", \"availability_hint\", \"official\", or \"new_item\"."
    • changedInput schema / properties / note / description
      Previous value: -"補足（任意）"New value: +"Anything else worth knowing. Optional."
    • changedInput schema / properties / proposed_value / description
      Previous value: -"提案する値"New value: +"The correct value (or, for a new item, its name and details)."
    • changedInput schema / properties / sku_id / description
      Previous value: -"対象SKU_ID（任意。新規商品の提案なら空でよい）"New value: +"The item's sku_id. Leave empty to suggest a new item."
    • changedInput schema / properties / source_url / description
      Previous value: -"根拠となる一次情報URL（任意）"New value: +"URL of a primary source that confirms it. Optional but strongly preferred."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the key behavioral trait that submissions are reviewed by hand before any catalog change occurs. It also recommends a primary source and states the return shape as {accepted, correction_id}, which is meaningful context for a non-read-only submission tool.

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?

The description is compact and front-loaded, moving from purpose to example to source guidance to return value. The example is useful and every sentence contributes without redundancy.

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

Completeness5/5

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

For a five-parameter submission tool with no output schema, the definition covers the essential context: what to submit, which fields are involved, what source is preferred, that review is manual, and what the response contains.

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 100%, so all five parameters are already documented. The description still adds value through a concrete example and by clarifying what counts as a primary source, though it does not significantly extend the schema's parameter semantics.

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 states a specific verb and resource: report a mistake or missing item in the catalog. It immediately distinguishes this submission/reporting action from the sibling discovery, estimation, and resolution tools.

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 description makes the intended use clear: submitting corrections for catalog mistakes or missing items. It does not explicitly name alternatives or exclusions, but the context is strong enough that an agent would not confuse it with the other sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All KH Merch Graph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources