Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reverb_price_guide

Fetch a gear model's Reverb Price Guide to view monthly average sale prices, finish/year variants, and recent sales. Filter by condition or date range for accurate pricing research.

Instructions

Get a gear model's Reverb Price Guide detail. Returns one gear model's Reverb Price Guide detail: its specific finish/year variants, monthly average sale-price history, and a page of individual recent sales. slug is the model's slug, from reverb-price-guide-search's own models[].slug field. canonical_product_id optionally scopes to one specific variant from this model's own canonical_products[].id field (from a prior call without it); omitting it aggregates price history and recent sales across every variant, a broader, more heavily-sampled view. condition optionally scopes by Reverb's own Price Guide condition scale (listed below) -- a separate, 6-value enum from reverb-search's own listing condition field. range selects how far back the price history/recent-sales window looks. An unknown slug returns a typed not-found error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesModel slug, from reverb-price-guide-search's own models[].slug field
limitNoRecent sales to return, defaults to 24, maximum 100
rangeNoDate-range window, defaults to years_1
conditionNoPrice Guide condition filter
canonical_product_idNoSpecific finish/year variant id, from this model's own canonical_products[].id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden. It does disclose the return shape, the aggregation trade-off when canonical_product_id is omitted ('broader, more heavily-sampled view'), and the error behavior ('unknown slug returns a typed not-found error'). It omits auth/rate-limit/pagination details, so it is strong but not complete for a zero-annotation tool.

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?

Front-loaded with the operation and return contents before diving into per-parameter scoping. It is one dense paragraph with heavy em-dash usage, which is informative but slightly run-on; nearly every clause earns its place.

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 annotations and no output schema, the description does the heavy lifting well: it describes the returned fields, the variant-aggregation behavior, and the error case. It is close to complete for a 5-param read tool, missing only pagination/limit semantics and any auth notes.

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 coverage is already 100%, so baseline is 3. The description earns above baseline by adding meaning the schema does not: the provenance of slug, the aggregation semantics of omitting canonical_product_id, the fact that condition is a distinct enum from the listing condition scale, and what range controls. Only 'limit' is left to the schema.

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 and resource ('Get a gear model's Reverb Price Guide detail') and immediately enumerates the returned payload (finish/year variants, monthly average sale-price history, recent sales). This is clearly distinguishable from sibling reverb-search (listings) and reverb-price-guide-search (which supplies the slug).

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?

Explicitly routes the agent: slug comes from reverb-price-guide-search's models[].slug, canonical_product_id comes from a prior call's canonical_products[].id, and condition is called out as a separate 6-value scale from reverb-search's listing condition field. The when-to-use and cross-tool dependency chain is fully spelled out.

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

Deploy Server

Other Tools