Skip to main content
Glama
Sign In
Goofish MCP Server

Goofish MCP Server

by mercy719
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

monitor_keyword

Monitor a keyword on Xianyu to track listing changes and pricing trends via normalized snapshots.

Instructions

Return a normalized Goofish/Xianyu keyword snapshot for monitoring.

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

Input Schema

NameRequiredDescriptionDefault
keywordYes
max_itemsNo
dedupe_keyNoitem_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral aspects. It fails to mention whether the tool is read-only, cached, or has side effects. The term 'snapshot' implies a point-in-time view, but no further context is given.

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

Conciseness3/5

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

The description is a single short sentence, which is concise in length but lacks sufficient detail. It could be restructured to include essential information without being overly verbose.

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

Completeness1/5

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

With no output schema, no parameter descriptions, and no annotations, the description is critically incomplete. It does not specify the format or content of the snapshot, making it hard for an agent to use effectively.

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

Parameters1/5

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

Schema coverage is 0% with no parameter descriptions in the schema. The description does not explain any of the three parameters (keyword, max_items, dedupe_key), leaving their purpose ambiguous.

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 it returns a normalized keyword snapshot for monitoring, identifying the action and resource. However, it does not explain what 'normalized' means or how it differs from similar tools like search_items, which also return keyword-related results.

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?

The description offers no guidance on when to use this tool versus alternatives like search_items or get_item_detail. It only mentions 'for monitoring' without clarifying conditions or exclusions.

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

Deploy Server

Other Tools