Skip to main content
Glama

All-time highs

all_time_highs
Read-onlyIdempotent

Use this when the user asks which cards in one game are at a record price. Returns cards that set their highest market price since TickerMint began tracking the game (February 2024 for Pokemon, One Piece and Lorcana; later for the others, see tracked_since) in the last 7 days and still hold it, with the date of the high, in USD. For a card released before that day it is not an all-time high: each card's high_is_all_time and high_scope say which it is.

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

Input Schema

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

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 200."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation, so the description does not need to repeat safety details. It adds valuable behavioral context about the tracking start date, the 7-day recency window, the condition that the high must still hold, USD pricing, and the `high_is_all_time` caveat for older cards.

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?

The description is appropriately front-loaded with the primary use case and then supplies the necessary definitional detail. It is slightly dense but every sentence supports correct interpretation of what counts as an all-time high.

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?

Given that an output schema exists and annotations cover safety traits, the description supplies the missing domain logic: the tracking period, the recency condition, the holding condition, currency, and the release-date caveat. That is enough for an agent to invoke and interpret the tool correctly.

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 100%, so the enum and limit are already documented. The description still adds meaning by explaining per-game tracking start dates, noting that non-Pokemon/One Piece/Lorcana games have later coverage, and pointing to `tracked_since` for exact dates.

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 states a specific verb and resource: returns cards in one game that set a record market price. It clearly establishes the scope as an all-time-high list and implicitly contrasts with `all_time_lows` by specifying highest market price.

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?

It gives an explicit trigger: use when the user asks which cards in one game are at a record price. It does not name alternatives such as `all_time_lows` or `most_valuable`, but the usage context is clear enough to select the 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