Skip to main content
Glama
Japan Used Camera Market MCP Server

Japan Used Camera Market MCP Server

by Enu27

Current price stats per model

price_stats

Summarize in-stock used camera prices by model: listing count, min/median/max in JPY and USD, shop and condition breakdowns, and the cheapest listing.

Instructions

Per-model price summary of in-stock listings right now: count and min / median / max (JPY and USD), broken down by shop and by normalized condition grade, plus the cheapest listing. Use keywords to stay fast (~1–4 min).

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": "price_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandsNoExact brand names, e.g. ["Leica", "Nikon", "FUJIFILM"].
gradesNoNormalized condition grades, best to worst: NEW > A > AB+ > AB > AB- > B > ASIS > PARTS.
sourcesNoShops: fujiya (full used stock), sanpou (full used stock), naniwa (new arrivals only), hardoff (Hard Off Off Mall cameras + lenses on sale, ~16,000). Default: all four.
keywordsNoMatch any of these in brand + title (case-insensitive, English or Japanese), e.g. ["Leica M6", "X100VI"].
maxItemsNoListings to read before summarizing (0 = all; a full read of all shops takes ~4 min).
maxPriceJpyNo
minPriceJpyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses latency (~1–4 min), that only in-stock listings are counted, and exactly what aggregates are returned. It does not explicitly state read-only behavior or rate limits, but the latency warning is the operationally important trait for a long-running read.

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?

A single dense sentence, front-loaded with the core purpose and return contents, ending with the actionable performance hint. The parenthetical currency and timing details earn their space, though the sentence is long enough to be slightly harder to scan.

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?

With no output schema and no annotations, the description effectively substitutes for one by enumerating the returned statistics and their groupings. The main residual gap is the two undocumented price-bound filters, plus no explicit statement of read-only semantics for a 7-parameter tool.

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 71%, so the baseline is 3, and the description adds real value on top: it links keywords to reduced runtime and maps the shop/condition breakdown outputs back to the sources and grades filters. minPriceJpy and maxPriceJpy remain undocumented in both schema and description, which keeps it below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely (per-model price summary of in-stock listings) and enumerates the computed statistics (count, min/median/max in JPY and USD, per-shop and per-grade breakdowns, cheapest listing). That distinguishes it from search_listings and price_history by implication, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for aggregate current pricing rather than listing retrieval or historical trends. The only explicit guidance is the performance tip to use keywords to stay fast, with no when-not-to-use conditions or named alternatives.

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