Skip to main content
Glama

TickerMint

by cards.tickermint.api
OverviewDiscussionsAdmin

Biggest movers

movers
Read-onlyIdempotent

Use this when the user asks which cards in one game rose or fell the most recently. Returns the biggest percentage moves over the last days (1 to 90) for cards worth $5 or more, with the start and end market price in USD. Describes past moves only; not a prediction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook-back window, 1 to 90 days.
gameNoCard game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam.pokemon
limitNo1 to 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window, 1 to 90 days."
    • 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 100."
  2. First observed

TDQS

A4.3/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 context beyond that: the $5 minimum value filter, the 1-90 day window, that start and end market price in USD are returned, and that it is descriptive of past moves rather than predictive.

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 use case, then output semantics, then the non-prediction caveat. No sentence is filler.

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 return values need not be spelled out, yet the description still summarizes what comes back (biggest percentage moves with start/end USD price). Nothing an agent needs to call this correctly is missing.

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 the schema already documents days, game, and limit; the description only restates the 1-90 range for days and adds the $5 worthiness threshold. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb+resource+scope: the biggest percentage movers in a single game over a recent window. It is readily distinguishable from siblings like all_time_highs/all_time_lows (absolute extremes) and price_history (single-card series).

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 an explicit trigger ("Use this when the user asks which cards in one game rose or fell the most recently"). It does not name alternative siblings or state when NOT to use it, but the trigger condition is unambiguous.

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