Skip to main content
Glama

Yahoo! Auctions product

run_yahoo_auctions_products
Read-onlyIdempotent

Get a Yahoo! Auctions Japan catalog product by id or URL: lowest current and buy-it-now price and the live auctions matched to that product. Flat 5 points per successful run.

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": {
      "product": "<product>"
    },
    "name": "run_yahoo_auctions_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesCatalog product ID or URL. e.g. a9f58050a0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, open-world). The description adds useful context beyond annotations by disclosing the flat cost ('Flat 5 points per successful run') and summarizing the returned data (prices and matched live auctions). It does not cover auth requirements or error behavior, but those are less critical here.

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?

Two compact sentences, front-loaded with the action and resource, then the return data and cost. No filler or repetition.

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

Completeness5/5

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

For a single-parameter read-only lookup with full schema coverage and annotations, the description supplies the remaining needed context: scope (Japan), what is returned, and cost. No output schema exists, but the description adequately explains the useful return contents.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, so the schema already documents that it accepts a catalog product ID or URL with an example. The description restates the same meaning ('by id or URL') without adding format details, so the baseline of 3 is appropriate.

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?

The description uses a specific verb ('Get') and resource ('Yahoo! Auctions Japan catalog product by id or URL'), and it explicitly states the returned data (lowest current and buy-it-now price, live auctions matched to that product). This distinguishes it from sibling item-search tools without needing to open schemas.

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

Usage Guidelines4/5

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

The phrase 'by id or URL' gives a clear condition for when to use this tool, implying it is for direct product lookup rather than keyword discovery. However, it does not explicitly name alternatives such as run_yahoo_auctions_items_search or state when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.