Skip to main content
Glama

Collection movers

collection_movers
Read-onlyIdempotent

The cards in your SlabLineage collection whose SlabLineage price per card rose or fell the most over the last 7 or 30 days: the price then (since) and now in USD, the change and the percent. Per-card prices, not your collection's total value (that is my_collection_summary).

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

Input Schema

NameRequiredDescriptionDefault
daysNo7 or 30 (default 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds substantial value by spelling out the returned fields (price then/since, now in USD, change, percent) and the 7/30-day window. It does not disclose how many movers are returned or whether gainers and decliners are ranked together, which is the one behavioral gap.

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?

A single front-loaded sentence that leads with the resource and metric, then the returned fields, then the disambiguation parenthetical. Dense but every clause carries information; the parenthetical clarification of what it is not is well placed.

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 usefully enumerates the return fields and the time window, which is most of what an agent needs for a one-parameter read tool. The remaining gap is result cardinality/ordering (how many movers, ranked how), which affects interpretation of the output.

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% and the single enum parameter already documents 7 or 30 with a default of 7. The description restates the same window in prose without adding format, boundary, or edge-case meaning, so the baseline 3 applies.

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?

Names a specific resource (the cards in your SlabLineage collection) and a precise metric (largest price rise/fall per card over 7 or 30 days), and explicitly contrasts with my_collection_summary's total-value figure so the agent can distinguish the two without opening a schema.

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?

Explicitly excludes the total-portfolio use case and routes it to my_collection_summary, which is a genuine alternative-with-condition. It does not state prerequisites (e.g., that the collection must contain cards with price history), but the usage context is clear.

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