Skip to main content
Glama

Search live PokeLances listings

search_store
Read-onlyIdempotent

Search existing public listings on pokelances.com to detect duplicates and compare prices before drafting a new card listing.

Instructions

Search what is already listed on pokelances.com (public, read-only). Use it to spot duplicates and compare prices before drafting.

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

Input Schema

NameRequiredDescriptionDefault
setNoSet name to narrow the search
nameYesCard or product name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds useful context by calling the source 'public' (no auth implied) and scoping results to live listings. It says nothing about result volume, ranking, pagination, or whether sold/expired listings appear — meaningful gaps for a search tool.

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 short sentences, no filler: what it searches first, then why to use it. Nothing is repeated from the title or schema.

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?

For a two-parameter read-only search with no output schema and full annotation coverage, the description gives enough to call it correctly. 'Compare prices' hints that listings include price data, though the actual result shape and result limits remain unstated.

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 coverage is 100% with both 'name' (required) and 'set' documented inline, so the schema carries parameter meaning. The description adds no detail on how 'set' narrows results or how matching is done (exact vs fuzzy), so it is a baseline 3.

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 and resource (search live listings on pokelances.com) and pins the scope with '(public, read-only)' and 'what is already listed', which separates it from a card-catalog search like search_cards. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

'Use it to spot duplicates and compare prices before drafting' gives a concrete situation and implicitly routes the agent toward create_draft after searching. There are no explicit when-not conditions or named alternatives, so it stops short of full routing guidance.

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