Skip to main content
Glama
Sign In

KH Merch Graph

by io.github.marleyhereicome-cpu
OverviewDiscussionsAdmin

Identify a marketplace listing

resolve_listing
Read-onlyIdempotent

Identify a Kingdom Hearts, Demon Slayer and One Piece item from a marketplace listing (Mercari, Yahoo! Auctions, Suruga-ya, Mandarake, eBay…). Paste the listing title as-is (Japanese or English), e.g. {title: "一番くじ キングダムハーツ A賞 ソラ フィギュア 箱なし", price_jpy: 4500}. Returns candidates[] (sku_id, name_en, confidence 0-1, why, source_url, page_url = the item's page on merchgraph.app; several when the title is ambiguous), weak_matches[] when unsure, conditions[] (Japanese condition words such as 未使用/箱なし explained), flags[] (bootleg caution notes, not a verdict), price (original price and listing-to-original ratio when price_jpy is given), shipping (whether a shipping-forwarding service is needed from abroad; set platform for a precise answer; for Mercari/Suruga-ya a note that Mercari's global app may allow direct purchase in some countries), acquisition notes and next_checks_en (what to ask the seller). Listing text is not stored. For many listings at once use resolve_listings_batch.

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": {
      "title": "<title>"
    },
    "name": "resolve_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
srcNoTraffic-source tag for usage statistics, used by the website (optional; only the tag and time are logged). Agents can omit it.
urlNoListing URL. Optional; not stored and not fetched.
titleYesThe listing title, copied as-is (required).
platformNoWhere it is listed. Optional.
price_jpyNoListing price in Japanese yen. Optional; enables the comparison with the original price.
descriptionNoPart of the listing description, e.g. condition notes such as 開封済み. Optional; improves condition and bootleg checks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"説明文の抜粋（任意）"New value: +"Part of the listing description, e.g. condition notes such as 開封済み. Optional; improves condition and bootleg checks."
    • changedInput schema / properties / platform / description
      Previous value: -"出品プラットフォーム（任意）"New value: +"Where it is listed. Optional."
    • changedInput schema / properties / price_jpy / description
      Previous value: -"出品価格（円、任意）"New value: +"Listing price in Japanese yen. Optional; enables the comparison with the original price."
    • changedInput schema / properties / src / description
      Previous value: -"計測用の流入元タグ（任意）。Web版チェッカーのURLパラメータ?src=から渡される。src自体と日時のみ利用ログに残す"New value: +"Traffic-source tag for usage statistics, used by the website (optional; only the tag and time are logged). Agents can omit it."
    • changedInput schema / properties / title / description
      Previous value: -"出品タイトル（必須）"New value: +"The listing title, copied as-is (required)."
    • changedInput schema / properties / url / description
      Previous value: -"出品URL（任意・サーバー側では保存しない）"New value: +"Listing URL. Optional; not stored and not fetched."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description piles on real behavioral context: listing text is not stored, ambiguous titles return several candidates with confidence scores, flags are caution notes rather than verdicts, and shipping answers require platform to be precise. That is precisely the kind of context annotations cannot carry.

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?

Front-loaded with purpose, then the example, then a densely packed return-value enumeration. Every sentence carries information given there is no output schema, but the long parenthetical field list makes it a single heavy block that would read better as a short list.

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?

With no output schema, the description takes full responsibility for explaining return values — candidates, weak_matches, conditions, flags, price, shipping, next_checks_en — and it also states the privacy behavior of listing text. Nothing an agent needs to call this correctly is missing.

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 baseline is 3; the description goes further by demonstrating the calling convention ('paste the title as-is', with a worked Japanese example) and by tying parameters to outcomes (price_jpy unlocks the listing-to-original ratio, platform sharpens the shipping answer). Some of that duplicates the schema's own parameter descriptions, which keeps it from a 5.

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?

States a specific verb ('Identify') plus the exact resource (an item from a marketplace listing) and enumerates the supported marketplaces. It also names the sibling it is not (resolve_listings_batch), so an agent can separate single-item identification from bulk resolution without opening either schema.

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?

Clear usage context: paste the listing title as-is in Japanese or English, optionally add price/platform/description, and route many listings at once to resolve_listings_batch. Explicit exclusions (when not to use this, e.g. versus explain_product or estimate_landed_cost) are absent, but the primary alternative is called out.

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