Skip to main content
Glama

RipSeek

What people just pulled

list_recent_pulls
Read-onlyIdempotent

Lists the newest pack openings on Collector Crypt across every site that sells its packs, newest first (from the latest ~200): card, insured value, rarity, pack and its price, how many times the pack price the card was worth, and when. Use it to show what people are really getting right now, optionally for one pack, one rarity or above a value; use search_cards for cards still waiting in a pool. Read-only; the feed is at most 30 seconds old and wallets are shortened.

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

Input Schema

NameRequiredDescriptionDefault
codeNoPack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100.
limitNoHow many pulls to return, 1 to 50 (default 20).
rarityNoOnly pulls of this rarity, e.g. epic.
min_valueNoOnly cards worth at least this many US$, e.g. 100.

Output Schema

NameRequiredDescriptionDefault
noteNo
pullsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, yet the description still adds genuinely new context: the feed is at most 30 seconds old, wallets are shortened for privacy, and results come from a bounded pool of the latest ~200 pulls. It stops short of describing how that cap interacts with deep queries, but the behavioral picture is materially richer than the annotations alone.

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?

Dense but front-loaded: the verb and resource lead, then scope, then returned fields, then the alternative. A few phrases such as 'what people are really getting right now' are slightly chatty, but nothing is redundant enough to cut.

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?

Output schema exists so return values need no explanation, annotations cover the safety profile, and all four parameters are fully described in the schema. The description fills the remaining gaps an agent would need (freshness, privacy, result window) before calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns an extra point by noting the ~200-pull window that all filters operate over and by summarizing the filterable axes (one pack, one rarity, or above a value), which affects how an agent should reason about limit and min_value rather than merely restating them.

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 verb (lists) and resource (newest pack openings on Collector Crypt), states scope across every site, ordering (newest first), and the bounded window (latest ~200). It also enumerates returned fields and explicitly contrasts with search_cards, so the agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ('show what people are really getting right now'), explains how the optional filters map to that use case, and names the alternative tool with the condition that selects it ('use search_cards for cards still waiting in a pool').

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