RocketVault Public Knowledge and Marketplace

Get an active RocketVault listing

get_marketplace_listing

Read-only

Retrieve current public card, approved listing image, condition, asking price, availability, known shipping terms, freshness, and canonical URL for one exact listing ID. Inactive, sold, reserved, unavailable, or unknown listings return a null listing. This does not provide a checkout total or sold-price valuation.

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": {
      "id": "<id>"
    },
    "name": "get_marketplace_listing"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Exact public marketplace listing ID, usually returned by search_marketplace_listings.

Output Schema

Name	Required	Description	Default
`listing`	Yes
`marketplace_available`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: inactive, sold, reserved, unavailable, and unknown listings all return a null listing rather than an error, which is essential for the agent to interpret the result correctly.

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?

Two sentences, front-loaded with the verb and scope, with the failure mode immediately after. The field enumeration is somewhat redundant given an output schema exists, which keeps it from a 5, but nothing is filler.

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 scope, the null-return edge case, and explicit non-capabilities, and an output schema handles return-value detail. An agent has enough to call it and interpret both hit and miss results without guessing.

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 schema already explains the ID format and that it usually comes from search_marketplace_listings. The description reinforces the 'exact' nature of the ID but adds no format, validation, or provenance detail beyond the schema, 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?

States a specific verb (Retrieve) and a precisely scoped resource (one exact listing ID) and enumerates the returned fields. An agent can distinguish this from search_marketplace_listings purely from the 'one exact listing ID' framing.

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?

The 'one exact listing ID' framing implicitly sets the precondition (you already have an ID), and the closing sentence explicitly excludes adjacent uses (checkout total, sold-price valuation). It stops short of naming search_marketplace_listings as the alternative for discovery, relying on the schema for that pointer.

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?