Skip to main content
Glama

All-time lows

all_time_lows
Read-onlyIdempotent

Use this when the user asks which cards in one game are at their lowest price or have crashed. Returns cards worth $5+ sitting at their lowest market price since TickerMint began tracking (all-time for cards released after that day, see each card's low_scope) after falling at least 50% from their high, with the high and the percent below it, in USD.

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_lows"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral substance beyond that: a $5+ price floor, a minimum 50% decline from the high, the low_scope caveat for cards released after tracking began, and USD as the currency — all of which determine what comes back. It does not state ordering or result-shape, but an output schema exists to cover that.

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 sentences, with the usage trigger front-loaded before the filter semantics. The second sentence is dense — nested parenthetical and the `low_scope` reference — but every clause defines a real inclusion criterion, so nothing is wasted.

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?

For a two-parameter, read-only screening tool with an output schema and full annotation coverage, the description supplies everything an agent needs to decide when to call it and what the results mean, including the threshold logic that cannot be inferred from the schema.

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%, so both parameters (game with its enum, and limit) are already documented. The description implies the single-game scoping of `game` and mentions USD, but adds no syntax or guidance for `limit` beyond what the schema states. Baseline 3 applies when the schema carries the parameter burden.

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 specific screening operation on a specific resource: cards in one game sitting at their lowest market price, or that have crashed. It is immediately distinguishable from the sibling all_time_highs and from point-lookup tools like card_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 opens with an explicit trigger condition — 'Use this when the user asks which cards in one game are at their lowest price or have crashed' — which tells the agent exactly which user intent selects this tool. It stops short of naming alternatives or exclusions (e.g. 'use all_time_highs for the opposite screen'), so it is clear context without full routing guidance.

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