Skip to main content
Glama

Price history

get_price_history
Read-onlyIdempotent

The SlabLineage (SL Consensus) price of one card, day by day, for the last 7, 30 or 90 days, with the change over that period. Values are USD.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cardId": "<cardId>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo7, 30 or 90 (default 30).
cardIdYesSlabLineage card id (the number in https://slablineage.com/card/{id}).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond them: the valuation source (SlabLineage / SL Consensus), the currency (USD), and the fact that a period-over-period change value is returned alongside the series.

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?

One sentence, front-loaded with what is priced and the source, then scope, then the returned aggregate and unit. Nothing is redundant or padded.

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?

With no output schema, the description carries the return-value burden and does state the series, the change metric, and the currency for a 2-parameter tool. It stops short of describing the shape of the series (array of dated points) or behavior for cards with missing history, which would have made it fully complete.

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%, so both parameters are already documented in the schema, including the 7/30/90 enum and the cardId format. The description restates the same window options and scope ('one card') without adding format, default, or fallback behavior, so the baseline 3 is appropriate.

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?

The description names a specific resource (SL Consensus price of one card) and a specific shape (day-by-day series over 7/30/90 days plus change over the period), so an agent knows exactly what it retrieves. It does not name or contrast with the closest sibling, get_card_price (current price) or collection_movers, leaving the historical-vs-snapshot distinction to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: an agent can infer this is the tool for historical trend rather than a point-in-time price. There is no explicit when-to-use statement, no exclusion such as 'not for current price – use get_card_price', and no guidance on choosing between the 7/30/90 windows beyond the enum itself.

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