Skip to main content
Glama

TickerMint

by cards.tickermint.api
OverviewDiscussionsAdmin

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.

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive safety, yet the description adds crucial behavior: only highs set in the last 7 days that still hold, tracking start dates, USD currency, and the high_is_all_time/high_scope caveat. That is meaningful context an agent could not infer from annotations alone.

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 sentences, front-loaded with the trigger, then the return definition, then the important release-date caveat. The parenthetical tracking-date example is dense but earns its place by preventing a false all-time interpretation.

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?

An output schema exists, so the description need not enumerate return fields, and it still explains the temporal window, currency, and high-scope caveat. That is enough for an agent to call this correctly.

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 limit range are fully documented in the input schema. The description adds no new constraint or format detail for either parameter, so the baseline 3 applies when the schema carries parameter semantics.

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?

States a specific verb and resource: returns cards at their highest market price. The scope (one game, record price) separates it from generic pricing siblings, but it never names all_time_lows, so sibling differentiation is implied rather than explicit.

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?

Gives a clear trigger: 'Use this when the user asks which cards in one game are at a record price.' However, it offers no when-not conditions or named alternative, so an agent knows the intended situation but not what to choose instead for lows.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TickerMint toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources