Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_instant_pack_release

Retrieve Fanatics Collect Topps Instant Pack release details by checklist ID, including title, launch time, status, checklist link, published odds, and price when available.

Instructions

Fanatics Collect Topps Instant Pack release details. Returns a release's title, launch time, current status, checklist link and published odds by checklist ID. The price in cents appears when a price is published. Unknown checklists return 404. Discover the checklist ID with fanaticscollect-instant-pack-releases.

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": {
      "checklist_id": "<checklist_id>"
    },
    "name": "fanaticscollect_instant_pack_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
checklist_idYesChecklist UUID from Instant Pack releases

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden, and it discloses meaningful behavior: the returned fields, that price appears only when published, and that unknown checklists return 404. It does not mention authentication, rate limits, or caching, but the error and conditional-field behavior are genuinely useful disclosures.

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

Conciseness5/5

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

Four compact sentences, front-loaded with the resource and purpose, followed by return fields, edge cases, and the sibling pointer. No filler or redundancy.

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 exists, yet the description enumerates the return fields and the 404 failure mode, which is sufficient for an agent to use it correctly. Missing only peripheral operational details such as auth or rate limits.

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%, so the checklist_id parameter is already documented as a 'Checklist UUID from Instant Pack releases'. The description adds provenance (where to obtain the ID) but not format or validation detail beyond the schema, so the baseline of 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 and resource: returns details of a single Topps Instant Pack release, and names the sibling tool used to obtain the checklist ID. An agent can distinguish it from fanaticscollect_instant_pack_releases (the list) without opening either 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?

Explicitly routes the agent to fanaticscollect-instant-pack-releases to discover the checklist ID, establishing the prerequisite lookup step before calling this tool. It lacks an explicit 'do not use this when...' exclusion or a statement about batch usage, but the single-release context is clear.

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