Skip to main content
Glama
goofish-price-mcp

goofish-price-mcp

by SkySabre

list_watch_tasks

List configured Goofish watch tasks and review each task's keywords, price range, cron schedule, decision mode, and stored item count.

Instructions

列出监控端的蹲守任务(关键词、价格区间、cron、判定模式、已入库数量)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, yet it discloses only that tasks are listed. It says nothing about ordering, pagination, whether all tasks or only active ones are returned, whether any account/scope restriction applies, or what happens when no tasks exist. The field enumeration in parentheses duplicates information that the declared output schema already provides.

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 front-loaded sentence with the verb and resource first, followed by a compact field list; no filler or restated title. Slight waste in that the parenthetical field list repeats the output schema.

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?

The tool is genuinely simple (no parameters, output schema present), so the description does not need to explain return values. However, for a listing tool it omits the basic operational facts an agent would want — result set scope, ordering, and whether the list can be large — leaving it only minimally adequate.

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, so the baseline is 4; there is no parameter meaning for the description to add. Nothing in the description misleads about inputs.

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?

States a specific verb (列出/list) and a specific resource (监控端的蹲守任务 / watch tasks on the monitoring side), and the parenthetical enumerates what each task record contains (keyword, price range, cron, judgment mode, stored-item count). It is not confused with the siblings (get_price_stats, latest_items, market_overview), which operate on different resources, but it does not explicitly contrast itself with any of them.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to an alternative tool for a different view of watch tasks. The only implied usage is the tautology 'call this to see the watch tasks', which the agent could already infer from the name.

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