Skip to main content
Glama
Sign In

Merchgraph

by io.github.marleyhereicome-cpu
OverviewDiscussionsAdmin

Browse the catalog

discover
Read-onlyIdempotent

Browse the merchandise catalog (Kingdom Hearts, Demon Slayer and One Piece) by series, character, budget and purpose. Use it to answer "what merch exists for X?" or "gift ideas under ¥5,000". Example: {ip: "kingdom-hearts", character: "Sora", budget_jpy: 5000, purpose: "display"}. Omit ip to search every series. Returns items[] (sku_id, name_en/name_ja, official, original price msrp_jpy plus price_local/currency, price_basis, price_note_en for per-draw prices, region, availability_hint, typical_channels, source_url, page_url = the item's page on merchgraph.app) and total_matches. For a series that is not covered, items is empty and supported_series lists the covered ones. If a character has no solo merch (e.g. Xigbar), the result also has suggested_character_group and suggested_items for their group (e.g. Organization XIII). Lists catalog entries only; it does not mean anything is for sale right now. Use explain_product with a sku_id for full details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoSeries ID. Live series: "kingdom-hearts" (Kingdom Hearts), "kimetsu-no-yaiba" (Demon Slayer), "one-piece" (One Piece). Optional: omit to search all of them.
limitNoMaximum number of items to return (default 10). total_matches always gives the full count.
termsNoFilter by series vocabulary (factions, worlds, keyblades, songs…) found in item names, aliases or notes. Optional.
purposeNo"display" = figures, plush, prizes, acrylic stands; "wear" = apparel; "read" = books; "play" = games and cards; "any" (default).
characterNoCharacter name in English or Japanese, e.g. "Sora", "ソラ", "Organization XIII". Partial match. Optional.
budget_jpyNoMaximum original price in Japanese yen (overseas items are compared at a fixed rate), e.g. 5000. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds real behavioral context beyond them: results are catalog entries only and imply nothing about current availability, unsupported series return empty items plus supported_series, and characters without solo merch return suggested_character_group/suggested_items. That fallback behavior is not derivable from any structured field.

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 and usage before the dense return-field enumeration, and every sentence carries information. The long parenthetical field list (sku_id, name_en/name_ja, price_basis, ...) is heavy, but with no output schema it earns its place.

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 six-parameter, nested-object, no-output-schema tool, the description covers invocation, edge-case returns, and the handoff to explain_product. An agent could call this correctly and interpret empty results without opening the schema.

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 would be 3, but the description adds operational meaning: omitting ip searches every series, budget_jpy compares overseas items at a fixed rate, and it shows a complete example object. It stops short of explaining limit/terms interplay, which the schema already handles.

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+resource ("Browse the merchandise catalog") and immediately bounds scope to three named series plus the filter axes (series, character, budget, purpose). It is clearly distinguishable from explain_product, which it names as the detail-lookup 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 concrete when-to-use triggers in the user's own phrasing ("what merch exists for X?", "gift ideas under ¥5,000") plus a worked example invocation. It also routes the agent onward: "Use explain_product with a sku_id for full details," so the boundary between browsing and drilling down is explicit.

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

All Merchgraph 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