Skip to main content
Glama

Set prices

get_set
Read-onlyIdempotent

A Pokémon, One Piece or sports set's priced cards on SlabLineage, with each card's grade, SlabLineage price and card page, in card number order. Search by set name.

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

Input Schema

NameRequiredDescriptionDefault
gameNo
queryYesSet name, e.g. "151" or "Evolving Skies".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so safety is covered. The description usefully adds the return shape (grade, price, card page) and ordering, which matters since there is no output schema. It says nothing about result size limits or pagination for large sets, or behavior when no set matches.

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?

Two tight sentences with no filler, front-loading what the tool returns before the search instruction. Slightly awkward phrasing ('on SlabLineage') but no wasted content.

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?

For a two-parameter read tool with annotations and no output schema, the definition covers purpose, inputs and return fields adequately. The notable omission is any indication of result volume or pagination, which is material for a tool that returns an entire set.

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

Parameters4/5

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

Schema coverage is only 50% and the undocumented parameter is the 'game' enum; the description compensates by enumerating exactly the three supported games (Pokémon, One Piece, sports). It also reinforces the 'query' parameter as a set name, though it adds no format guidance beyond the schema's own example.

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 a specific resource and scope: priced cards for a whole set, listing the exact fields returned (grade, SlabLineage price, card page) and the sort order (card number). It also names the supported games. It does not explicitly differentiate itself from siblings like search_cards or get_card_price, so it stops short of a 5.

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?

'Search by set name' implies the lookup mode, and the mention of a whole set's cards implies this is the browse-a-set tool rather than a single-card lookup. There is no explicit when-not guidance or pointer to the alternative tool for individual card prices.

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