Skip to main content
Glama
goofish-price-mcp

goofish-price-mcp

by SkySabre

latest_items

Retrieve recently scraped in-sale second-hand listings with title, price, link, seller, and timestamp, sorted by scrape time. Filter by keyword, price range, or recommended-only status.

Instructions

列出最近蹲到的在售商品明细(标题/价格/链接/卖家/发布时间),按抓取时间倒序。

可按关键词、价格区间过滤;recommended_only=True 只看判定为推荐的商品。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordNo
max_priceNo
min_priceNo
recommended_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Because no annotations are provided, the description carries the full burden of behavioral disclosure. It usefully discloses the sort order, the returned fields, and what recommended_only means (只看判定为推荐的商品), but it never explains the limit parameter, the maximum allowed value or default behavior, or what window "最近" actually covers. As a read-only listing tool, the remaining risk is low, but the missing limit and time-window semantics are real gaps.

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?

Two tight lines with the resource and returned fields front-loaded, followed by filtering options; nothing is redundant. It is arguably a touch too terse, since the limit parameter and the recency window go unaddressed, but every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool with 0% schema coverage and no annotations, the description explains the main filters and the output fields, and an output schema exists so return values need no further explanation. Still missing are the meaning of limit, the definition of "最近" or the recency window, and a signal that this is a read-only listing; for a tool of this complexity, the description should say more.

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 description coverage is 0%, so the description must add meaning, and it does for keyword, min_price/max_price, and especially recommended_only, whose meaning it clarifies. Limit is the one parameter left entirely unexplained, so the description nearly compensates for the coverage gap.

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 a specific verb (列出) and resource (最近蹲到的在售商品明细), then enumerates the returned fields (标题/价格/链接/卖家/发布时间) and the sort order (按抓取时间倒序). This clearly distinguishes it from siblings like get_price_stats or market_overview, which aggregate rather than enumerate, though 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?

The filtering options (keyword, price range, recommended_only) imply when the tool is appropriate for a browsing use case. However, no explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named for cases such as wanting aggregates or stats.

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