Skip to main content
Glama

Find deals

find_deals
Read-onlyIdempotent

Graded Pokémon and One Piece cards with live marketplace listings well under the SlabLineage price right now. For each card: the grade, the SlabLineage price, how many live deals SlabLineage shows, and its card page. The listings themselves are in SlabLineage's Ending Soon list (dealsPage). Up to 10 cards, most deals at the top.

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

Input Schema

NameRequiredDescriptionDefault
gameNoLimit to one game.
gradeNoLimit to one grade, as text: "10" or "9".
queryNoCard or set name to narrow the results, e.g. "charizard".
companyNoLimit to one grading company.
maxSlPriceNoCards whose SlabLineage price is at most this many USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description correctly does not repeat that. It adds genuine value beyond the annotations: a hard cap of 10 cards, the ordering rule (most deals at top), the exact per-card fields, and the important caveat that listings themselves are not returned here but at dealsPage. The only gap is that the deal threshold is not quantified.

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?

Four short sentences, front-loaded with the result set, followed by result shape and then the dealsPage caveat. Wording is efficient, though the repeated 'SlabLineage' phrasing and the mid-sentence deflection to dealsPage slightly dilute a tight structure.

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?

With five optional filters, no output schema, and a fixed 10-result cap, the description supplies the return-field list and ordering rule that an output schema would otherwise provide. The one substantive omission is how the 'well under price' cutoff is computed, which leaves the agent unable to explain or predict inclusion criteria.

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% with three enums, so the schema already carries all parameter meaning including examples and ranges. The description adds no filter semantics beyond what the schema documents, which is the expected baseline of 3 when the schema does the work.

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 names the resource precisely (graded Pokémon and One Piece cards with live listings under the SlabLineage price) and describes the per-card payload, so an agent knows exactly what this returns. It stops short of naming a contrasting sibling such as get_card_price or search_cards, so the boundary 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 Guidelines3/5

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

There is an implicit usage hint: 'right now' plus the pointer that actual listings live in the Ending Soon list (dealsPage), which routes the agent to a follow-up call. However, there is no explicit when-to-use vs when-not guidance relative to pricing or search tools, and the selection criteria for a 'deal' (what 'well under' means) is never defined.

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.

Resources