Skip to main content
Glama
Sign In

KH Merch Graph

by io.github.marleyhereicome-cpu
OverviewDiscussionsAdmin

Identify several marketplace listings

resolve_listings_batch
Read-onlyIdempotent

Run resolve_listing on up to 5 listings in one call, e.g. when comparing search results from a marketplace. Example: {listings: [{title: "…", price_jpy: 3000}, {title: "…"}]}. Returns an array in the same order; each element has the same shape as a resolve_listing result (or {error} for that one listing only). For more than 5, split into several calls. For a single listing use resolve_listing.

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": {
      "listings": "<listings>"
    },
    "name": "resolve_listings_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingsYesListings to check (1–5); each takes the same arguments as resolve_listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / listings / description
      Previous value: -"出品の配列（1〜5件）。各要素は resolve_listing と同じ引数"New value: +"Listings to check (1–5); each takes the same arguments as resolve_listing."
    • changedInput schema / properties / listings / items / properties / description / description
      Previous value: -"説明文の抜粋（任意）"New value: +"Part of the listing description. Optional."
    • changedInput schema / properties / listings / items / properties / platform / description
      Previous value: -"出品プラットフォーム（任意）"New value: +"Where it is listed. Optional."
    • changedInput schema / properties / listings / items / properties / price_jpy / description
      Previous value: -"出品価格（円、任意）"New value: +"Listing price in Japanese yen. Optional."
    • changedInput schema / properties / listings / items / properties / src / description
      Previous value: -"計測用の流入元タグ（任意）。src自体と日時のみ利用ログに残す"New value: +"Traffic-source tag for usage statistics (optional; only the tag and time are logged)."
    • changedInput schema / properties / listings / items / properties / title / description
      Previous value: -"出品タイトル（必須）"New value: +"The listing title, copied as-is (required)."
    • changedInput schema / properties / listings / items / properties / url / description
      Previous value: -"出品URL（任意・サーバー側では保存しない）"New value: +"Listing URL. Optional; not stored and not fetched."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful behavior annotations don't carry: results come back in input order and match resolve_listing's shape, with per-item {error} objects so one bad listing does not fail the batch.

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?

Four tight sentences front-load the batch semantics, then the return shape, then the size rule, then the sibling pointer. The inline example uses ellipsis placeholders, which is slightly loose but does not waste space.

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 supplies the return contract (ordered array, resolve_listing shape, per-item errors) and the batch-splitting rule, so nothing an agent needs to call it 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 the baseline is 3, and the description goes beyond it by explaining that each array element takes the same arguments as resolve_listing and by showing an example payload with title and price_jpy. The 1-5 cardinality of the array is reinforced in prose.

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 and resource ('Run resolve_listing on up to 5 listings in one call') plus the batch size limit, which immediately separates it from the single-item resolve_listing sibling.

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?

Gives a concrete usage scenario ('when comparing search results from a marketplace') and explicit routing rules: use resolve_listing for a single listing, split into several calls above 5. Both the when and the when-not are stated.

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