RocketVault Public Knowledge and Marketplace

Search active RocketVault card listings

search_marketplace_listings

Read-only

Searches anonymous public active listings with structured card and budget filters. At least one card identity filter is required; field schemas describe exact and substring matching. Results include public listing IDs, freshness, and current asking prices rather than sold comps. More than 100 matches sets refinement_required=true and returns no next cursor. Availability and prices can change after retrieval.

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

Input Schema

Name	Required	Description	Default
`sort`	No		recent
`team`	No	Case-insensitive substring match against the stored team.
`year`	No	Exact card year.
`brand`	No	Case-insensitive substring match against the stored brand.
`grade`	No	Exact stored grade string, such as 10 or 9.5.
`query`	No	Full-text search across public listing card details; results are not exact-card matches by themselves.
`sport`	No	Case-insensitive exact match against the stored sport.
`cursor`	No
`player`	No	Case-insensitive substring match against the stored player name.
`max_year`	No	Inclusive upper bound for card year.
`min_year`	No	Inclusive lower bound for card year.
`parallel`	No	Case-insensitive substring match against the stored parallel.
`set_name`	No	Case-insensitive substring match against the stored set name.
`is_insert`	No
`is_rookie`	No
`page_size`	No
`raw_graded`	No
`card_number`	No	Exact card-number match; one leading # is ignored by the marketplace.
`is_numbered`	No
`is_autograph`	No
`accepts_offers`	No
`grading_company`	No	Case-insensitive exact grading-company match.
`max_price_cents`	No	Maximum asking price in USD cents.
`min_price_cents`	No	Minimum asking price in USD cents.

Output Schema

Name	Required	Description	Default
`listings`	Yes
`page_size`	Yes
`next_cursor`	Yes
`total_matches`	Yes
`refinement_required`	Yes
`marketplace_available`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, yet the description adds genuinely non-obvious behavior: anonymity of listings, a hard 100-match ceiling that flips refinement_required and suppresses the cursor, and a staleness warning that availability and prices change after retrieval. These are the failure modes an agent would otherwise hit blind.

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?

Five dense sentences with no filler, front-loading purpose before constraints and result shape. Each sentence carries a distinct fact (filter requirement, match semantics, return content, cap behavior, staleness), though the result-content sentence edges toward what the output schema already covers.

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?

Covers the operational essentials for a 24-parameter search: mandatory filter, pagination ceiling, and result nature. Since an output schema exists, return values need not be spelled out; the remaining gap is the undocumented optional parameters, which the description acknowledges only at a meta level.

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?

Adds a cross-parameter rule that no single field carries (a card identity filter is mandatory), and tells the agent that exact vs substring matching lives in the field schemas rather than repeating it. With 24 parameters and only 63% schema description coverage, this orientation is valuable, though it does not compensate for the ~9 undocumented fields such as page_size, cursor, and the boolean flags.

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?

Opens with a specific verb and resource ("Searches anonymous public active listings") and scopes it to structured card and budget filters, then clarifies it returns asking prices "rather than sold comps." That contrast is meaningful but it never names the sibling tools (get_marketplace_listing, search, fetch) it must be distinguished from, so an agent still has to infer the boundary.

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?

Provides one strong precondition — "At least one card identity filter is required" — and explains the refinement_required cap, which shapes how the tool is called. However, it gives no explicit when-to-use/when-not guidance relative to get_marketplace_listing or fetch, so the choice between them is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RocketVault Public Knowledge and Marketplace tools Inspect

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

Need Help?