Skip to main content
Glama

Most valuable cards

most_valuable
Read-onlyIdempotent

Use this when the user asks for the most expensive or most valuable cards in one game right now. Returns up to 25 singles ranked by today's raw market price (USD) with set and printing. Raw prices only, not graded values.

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

Input Schema

NameRequiredDescriptionDefault
gameNoCard game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world.pokemon
limitNo1 to 25.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam."New value: +"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world."
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "pokemon",
      -  "one-piece",
      -  "lorcana",
      -  "riftbound",
      -  "yugioh",
      -  "gundam"
      -]New value: +[
      +  "pokemon",
      +  "one-piece",
      +  "lorcana",
      +  "riftbound",
      +  "yugioh",
      +  "gundam",
      +  "fusion-world"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / game / description
      Added value: +"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam."
    • addedInput schema / properties / game / enum
      Added value: +[
      +  "pokemon",
      +  "one-piece",
      +  "lorcana",
      +  "riftbound",
      +  "yugioh",
      +  "gundam"
      +]
    • addedInput schema / properties / limit / description
      Added value: +"1 to 25."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's contribution is complementary: the 25-item cap, USD currency, ranking basis (today's raw market price), and the singles-only/no-graded limitation. It adds meaningful scope and data-freshness context rather than restating annotations, though tie-breaking and pagination behavior remain unstated.

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?

Three tight sentences with zero filler: trigger first, then result shape, then the graded-price exclusion. Every clause carries information an agent can act on, and the most decision-relevant constraint is front-loaded.

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 only two parameters, full schema coverage, an output schema, and rich annotations, the description covers what an agent still needs to know (time-sensitivity, currency, singles-only, no grading). Only minor gaps remain, such as what happens for non-card requests or ranking ties, which are unlikely to block correct invocation.

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% — the game enum and the limit range (1 to 25) are fully documented in the schema. The description echoes these with 'one game' and 'up to 25' but adds no syntax or format detail beyond what the schema already provides, so the baseline 3 applies.

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 names a concrete resource and ordering: singles ranked by today's raw market price in USD, scoped to one game, capped at 25. It also distinguishes itself from the graded_price sibling by explicitly excluding graded values, and from time-series siblings via 'right now'/'today's'.

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 opening clause gives a direct trigger ('Use this when the user asks for the most expensive or most valuable cards in one game right now'), which is clear when-to-use guidance. It stops short of naming alternatives outright, but the explicit 'Raw prices only, not graded values' exclusion effectively routes the agent away from the graded 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.

Resources