Skip to main content
Glama
Sign In

TickerMint

by io.github.seankarltonlee
OverviewDiscussionsAdmin

Market index

market_index
Read-onlyIdempotent

Use this when the user asks how one game's card market as a whole is doing, or for the TickerMint index (for example the TickerMint Pokemon 100). Returns the index level with its date, its 1-day, 7-day, 30-day and year-to-date change in percent, its all-time high, the largest constituents, the latest dated facts from the TickerMint wire, and a citation line. The index is an equal-weighted average of the raw TCGplayer market prices of the game's priciest singles that trade, rebalanced monthly, base 1,000. Past prices only; not a forecast.

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

Input Schema

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

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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the methodology (equal-weighted average of raw TCGplayer market prices of the priciest tradable singles, rebalanced monthly, base 1,000) and sets expectations that results are backward-looking, not a forecast. That is substantial behavioral context not present in the annotations; only the response shape is left to the output schema.

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 text is well front-loaded: usage trigger first, then output contents, then methodology and a caveat. It is slightly longer than needed because it enumerates return fields that the output schema already documents, but 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?

For a single-parameter, read-only lookup with a full output schema, the description covers the trigger, the methodology, and the scope limitation. An agent has everything required to select and call it 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?

There is a single `game` parameter with 100% schema coverage and a full enum, so the schema already carries the semantics. The description references "one game" and gives an example game but adds no further constraint or default behavior beyond what the schema states.

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 the specific resource (a game's card market index / the TickerMint index, e.g. TickerMint Pokemon 100) and the verb-like action (report how the market as a whole is doing). This clearly separates it from single-card siblings like card_price or graded_price, which operate on individual cards.

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?

"Use this when the user asks how one game's card market as a whole is doing" is an explicit, actionable trigger tied to an aggregate-market question. It also implies when not to use it (individual card questions belong to card_price), though it never names a sibling alternative or states exclusions directly.

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