Skip to main content
Glama
furima-mcp
by fxia0018

sold_price_stats

Read-only

Calculates count, min, quartiles, median, max and mean of recent sold prices per site on Mercari, Yahoo! Auctions and Rakuma to judge whether a price is fair.

Instructions

What an item actually sells for: statistics over recently sold listings.

Reads the most recent sold listings from Mercari, Yahoo! Auctions (final prices) and Rakuma, and returns count, min, p25, median, p75, max and mean overall and per site, plus a few recent sales as examples.

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": {
      "query": "<query>"
    },
    "name": "sold_price_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keyword, ideally in Japanese.
sitesNoSites with sold history to use. Default: mercari, yahoo, rakuma.
sampleNoSold listings to read per site before filtering.
excludeNoDrop listings whose title contains any of these words (case-insensitive).
max_priceNoMaximum price in JPY.
min_priceNoMinimum price in JPY.
match_all_wordsNoKeep only listings whose title contains every word of the query (ignoring width, case, spaces and hyphens). The sites' own search is fuzzy: 'PS5 CFI-2000' also returns PS5 games.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds real value by disclosing where data comes from, that 'sample' listings are read per site before filtering, and exactly what statistics are returned (count, min, p25, median, p75, max, mean overall and per site, plus example sales). It says nothing about empty-result behavior or latency across three sites.

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?

The purpose sentence is front-loaded and efficient, and the second paragraph cleanly enumerates sources and return values. Slightly verbose line-wrapping but no filler sentences.

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, the description carries the return-value burden and does so by listing the full statistic set and sample sales. It is nearly complete for a read-only aggregation tool; the remaining gap is behavior when no sold listings are found or when a site fails.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the schema, including the match_all_words rationale. The description only indirectly touches parameters by mentioning per-site breakdown; it adds no syntax or interpretation beyond the structured fields, so baseline 3 applies.

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 gives a specific verb and resource — computing price statistics over recently sold listings — and names the three data sources (Mercari, Yahoo! Auctions, Rakuma). The phrase 'what an item actually sells for' implicitly separates it from asking-price tools like check_price, but no sibling is named 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 by the framing: reach for this when you want realized sale prices rather than listed prices. There is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no routing to check_price, search_listings or get_listing.

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