Skip to main content
Glama

TickerMint

by io.github.seankarltonlee
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

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

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

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

Annotations already declare read-only, idempotent and non-destructive behavior, so the description is not carrying the safety burden. It adds genuinely non-obvious behavior: results are filtered to cards worth $5 or more and ranked by percentage rather than absolute price change, which materially affects how the agent interprets results.

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 short sentences: trigger first, then the returned metric and its filter, then the interpretive caveat. No restated title, no filler, and each sentence adds a distinct fact.

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?

An output schema exists, so return-shape explanation is not required, and the description supplies the ranking basis, price threshold and scope caveat an agent needs to present results correctly. Minor gap: no indication of whether a game with too few qualifying cards yields an empty set.

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% with per-parameter descriptions and an enum, so the schema already documents days, game and limit. The description restates the day range without adding syntax or defaults, and never mentions the limit parameter's effect on result size. 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 question the tool answers (which cards rose or fell the most) plus the exact metric returned: biggest percentage moves with start and end market price. That metric-based framing separates it cleanly from siblings like most_valuable and all_time_highs.

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?

Opens with an explicit trigger condition ('when the user asks which cards in one game rose or fell the most recently') and adds a scope exclusion ('describes past moves only; not a prediction'). It stops short of naming which sibling to use for alternate questions such as all-time extremes, which is why it is not a 5.

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