Skip to main content
Glama
goofish-price-mcp

goofish-price-mcp

by SkySabre

market_overview

Get a snapshot of all monitored keywords: average and lowest prices from the past day, total sample counts, and how long each watch task has been running.

Instructions

所有已监控关键词的行情速览:最近一天均价/最低价、累计样本量、运行时间。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, so the description carries the full disclosure burden; it does imply a read-only aggregation and names the exact metrics the result contains, which is useful. However, it says nothing about the freshness/latency of the data, what happens when no keywords are monitored, or how '最近一天' (last day) is anchored — all relevant for a tool whose entire output is a time-windowed aggregate.

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?

One sentence, front-loaded with the scope ('all monitored keywords') followed by the metric list, with zero filler. Every clause maps to something the caller actually needs to know before invoking.

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 parameters and an output schema present, the description need only establish purpose and scope, both of which it does, plus the metric set. The remaining gap is competitive positioning against get_price_stats and the meaning of the time window, which a one-line definition could reasonably have added.

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 tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals that no filtering or scoping arguments are needed by stating the scope is all monitored keywords.

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 states a specific verb+resource ('行情速览' / market overview) over a defined scope ('所有已监控关键词' / all monitored keywords) and enumerates the metrics returned (last-day average price, lowest price, cumulative sample count, runtime). It is clear on its own, but it never distinguishes itself from the sibling get_price_stats, which by name alone appears to cover adjacent price-statistics territory.

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 only implied: the word '速览' (quick overview) and the aggregate-all-keywords scope hint that this is the summary/dashboard entry point rather than a per-keyword deep dive. There is no explicit when-to-use statement, no exclusion, and no pointer to get_price_stats or latest_items as the alternative for detailed or fresh data.

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