Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alt_card_search

Search Alt's reference card-design catalog to locate a card design's asset_id without a live listing or sale, enabling population reports and recent sales lookups.

Instructions

Search Alt's reference card-design catalog. Searches Alt's reference card-design catalog -- a canonical catalog of card designs (one entry per year/brand/subject/card-number/variety combination), separate from live listings or sales. Useful for finding a card design's asset_id (to feed into alt-asset for a population report and recent sales) without already having a live listing or sale that references it.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search across card name, subject, brand, and variety
pageNo1-based page number, default 1
per_pageNoResults per page, default 24, max 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries full disclosure burden, and it does meaningful work: it defines what an entry represents (year/brand/subject/card-number/variety), clarifies the catalog is reference data separate from market data, and signals a read-only lookup. It does not describe return shape, ordering, or result limits, but the key behavioral framing an agent needs is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are near-verbatim duplicates ('Search Alt's reference card-design catalog. Searches Alt's reference card-design catalog...'), which wastes budget and delays the genuinely useful content. The remaining sentences are efficient and load-bearing, but the repetition is a clear structural flaw.

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?

No output schema or annotations exist, so the description must orient the agent, and it does: domain model, what a record represents, and the downstream handoff to alt_asset. For a zero-required-param search tool this is close to sufficient; only the return/pagination behavior is left entirely to the schema.

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 all three parameters (q, page, per_page) are already documented in the schema, including the fields q searches over. The description mentions the searchable dimensions but adds no syntax, matching behavior, or format guidance beyond the schema. Baseline 3 is appropriate.

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 ('Search Alt's reference card-design catalog') and then defines the catalog conceptually ('one entry per year/brand/subject/card-number/variety combination'). It explicitly separates itself from live listings or sales, so an agent can distinguish it from alt_search/alt_listing siblings without opening any schema.

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?

Gives concrete usage context: use it to recover a card design's asset_id and feed it into alt_asset for population reports and recent sales, and explicitly for the case where no live listing or sale references the design. It names a downstream sibling (alt_asset) but does not name the alternative listing-search tool to use when a listing does exist, so the when-not branch is implied rather than stated.

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