Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alt_asset

Get a card design's population report and recent raw sales to evaluate its rarity and market price by asset_id.

Instructions

Get one card design's population report and recent sales. Returns one card design's identity, full population report (across every grading company and grade Alt tracks), and a recent raw sales feed -- the "is this card actually rare, and what does it sell for" data for a specific card design, independent of any single listing. asset_id comes from a prior alt-search/alt-sold-listings/alt-card-search result's asset_id field. recent_sales has no per-transaction grade breakdown -- Alt does not expose one; see alt-sold-listings for per-grade sold prices on specific listings.

Input Schema

NameRequiredDescriptionDefault
asset_idYesThe card design's asset id, from a Search/SoldListings/CardSearch result's asset_id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 burden and does so reasonably well: it discloses the exact data returned and openly flags a data limitation (recent_sales has no per-transaction grade breakdown because Alt does not expose one). It does not mention auth needs or rate limits, but the surfaced limitation is genuine behavioral context.

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 core purpose and ends with the most actionable caveat and alternative. There is mild redundancy between 'population report and recent sales' and the subsequent enumeration, and the parenthetical/quoted asides make it denser than needed, but it is efficiently organized overall.

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?

With no output schema, the description must explain the return shape and does: identity, full population report, and recent sales feed. Combined with the param source and the cross-tool pointer, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the single asset_id param is already documented. The description reinforces the lineage (from a prior alt-search/alt-sold-listings/alt-card-search result's asset_id field), which is a slight value-add but largely duplicates 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+resource ('Get one card design's population report and recent sales') and enumerates exactly what is returned: identity, population report across every grading company/grade, and a recent raw sales feed. It distinguishes itself from siblings by positioning the data as 'independent of any single listing' and pointing to alt-sold-listings for the per-grade alternative.

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?

Frames the use case clearly ('is this card actually rare, and what does it sell for') and routes the agent to alt-sold-listings when per-grade sold prices are needed, plus tells where asset_id comes from. There is no explicit 'when not to use this' beyond the one alternative, so it stops short of full when/when-not guidance.

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