Skip to main content
Glama
goofish-price-mcp

goofish-price-mcp

by SkySabre

get_price_stats

Query second-hand Goofish/Xianyu price statistics for a keyword, returning average, median, lowest prices, daily trends, and cheapest listing links over a chosen lookback period.

Instructions

查询某关键词的闲鱼二手行情:均价/中位/最低价、按天价格趋势、最便宜的商品链接。

keyword 支持模糊匹配(如 "DDR4");days 为回看天数(1-365)。 样本 = 监控任务在搜索条件下每次运行实际看到的挂牌价。

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": {
      "keyword": "<keyword>"
    },
    "name": "get_price_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
keywordYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds genuinely non-obvious context about data provenance: the sample is made of asking prices that a monitoring task actually observed on each run, not an exhaustive market scrape. However, it does not say what happens when the keyword matches no monitored task or when the window has no samples; it also does not say whether the tool is read-only or whether it needs authentication, and there are no rate-limit notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short segments: it lists the outputs first, followed by the parameter notes and the provenance note that qualifies the data. There is no filler, and each sentence adds information that is not in the schema.

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?

An output schema exists, so the design does not require the description to spell out return shapes; nevertheless, the description still summarizes what is returned. Combined with the parameter notes and the sample-provenance semantics, an agent has enough information to call the tool correctly; the remaining gap is the missing explanation of empty-result behavior and of the dependency on existing monitor tasks.

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?

The schema description coverage is 0%, so the description has to explain both parameters, and it does: keyword is described as fuzzy-matchable with a concrete example ("DDR4"), and days as a lookback window constrained to 1-365. The only gap is that the 30-day default is left to the schema.

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 begins with a specific verb and resource: “查询某关键词的闲鱼二手行情”. It also names the exact outputs: 均价/中位/最低价, 按天价格趋势, and 最便宜的商品链接. This is far more specific than a restated title, but it never distinguishes the tool from the sibling market_overview, which plausibly overlaps with it.

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?

There is no explicit statement of when to use this tool instead of market_overview or latest_items; usage must be inferred. The closing line provides an implicit prerequisite: the sample comes from prices recorded by monitoring tasks that match the search condition, so a task must already exist. The condition that selects this tool is only implied, not stated.

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