Skip to main content
Glama

collectablespulse

Get AI-synthesized market valuations and intelligence for collectibles including sports cards, coins, comics, and more. Access endpoints for grading, authentication, investment signals, and selling guides.

Instructions

CollectablesPulse: Global collectibles market intelligence API. AI-synthesized valuations for sports cards, coins, comics, vinyl records, Pokémon/MTG/TCGs, sneakers, watches, signed memorabilia, and trading cards. Real-

Coverage: Global

Endpoints: • value ($0.10): Current market value by grade/condition • grade ($0.08): Grading service guide • authenticate ($0.10): Authentication guide — spot fakes, trusted services • invest ($0.15): Investment signal — buy/hold/sell with analysis • compare ($0.10): Head-to-head investment comparison • sell ($0.10): Where and how to sell for maximum value • storage ($0.08): Preservation and storage guide • insurance ($0.08): Collectibles insurance guide • population ($0.08): Population report and grade scarcity • provenance ($0.10): Provenance and ownership research • nft ($0.10): NFT contract safety & floor scan (on-chain GoPlus + market context)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNoCollectible description (e.g. '1952 Topps Mickey Mantle')
langNolang
chainNoethereum | base | polygon | arbitrum | optimism | bsc | avalanche (default ethereum)
gradeNoGrade or condition (e.g. 'PSA 10', 'CGC 9.8', 'raw Near Mint')
item1Noitem1
item2Noitem2
actionYesWhich endpoint to call. Options: value | grade | authenticate | invest | compare | sell | storage | insurance | population | provenance | nft
serviceNoPreferred service (PSA|BGS|CGC|PCGS|NGC|etc)
contractNoNFT contract address — enables the on-chain risk scan (recommended)
collectionNoCollection name — for floor/sentiment context when no contract is known
Behavior3/5

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

No annotations provided, so description must bear the burden. It mentions endpoints and costs, implying read-only queries, but does not explicitly state safety, failure modes, or side effects.

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 purpose, then a clear list of endpoints. Slightly verbose with repeated 'Collectibles' context, but well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks explanation of return values, default behaviors, or how parameters interact across endpoints. With 10 parameters and no output schema, more context is needed for full usability.

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 covers all parameters with descriptions (100% coverage). The description adds endpoint costs but does not significantly enhance parameter meaning beyond 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?

The description clearly states it is a collectibles market intelligence API with specific categories (sports cards, coins, etc.) and lists distinct endpoints. This differentiates it from the many sibling 'pulse' tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. With many similar sibling tools, explicit usage context is missing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/mcp-pulsenetwork'

If you have feedback or need assistance with the MCP directory API, please join our Discord server