Skip to main content
Glama
Sign In
Goofish MCP Server

Goofish MCP Server

by mercy719
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_items

Search Goofish items by keyword to retrieve structured item details, enabling keyword-based monitoring and comparison.

Instructions

Search Goofish/Xianyu items by keyword using a logged-in Playwright browser context. Example queries: iphone 15 pro, sony a7, dyson v12.

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

Input Schema

NameRequiredDescriptionDefault
keywordYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. Only mentions automation context but omits details on rate limits, blocking risks, session requirements, or return format. Insufficient for being the sole source.

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 with relevant examples, no fluff. Every part adds value.

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?

Describes the basic action and prerequisite, but for a 2-param search tool with no output schema, it should hint at return structure or pagination. Leaves agent guessing about results.

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

Parameters2/5

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

Schema coverage 0%, but description only mentions keyword via examples, not its format or required roles. Limit parameter and its default are completely ignored. Fails to compensate for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb 'Search' and resource 'Goofish/Xianyu items' via unique context 'logged-in Playwright browser context'. Distinct from siblings like get_item_detail or monitor_keyword.

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?

Implies prerequisite (logged-in Playwright context) but lacks explicit when-to-use vs alternatives like monitor_keyword or get_item_detail. Example queries help but no exclusion criteria.

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