Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticslive_instant_rips

Fetch a Fanatics Live show's active instant-rip state to track spot claim progress and the item being revealed; returns no break data when none is active.

Instructions

Get a Fanatics Live show's current instant-rip state. Returns a Fanatics Live show's current break's digital-instant-rip state: spot claim/rip progress and the currently revealing item, when a rip is actively in progress. current_break is omitted when the show has no active break at request time.

Input Schema

NameRequiredDescriptionDefault
idYesFanatics Live show id, the same id GET /fanaticslive/show/{id} takes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose real behavior: it reports spot claim/rip progress and the currently revealing item, and that current_break is omitted when there is no active break. It does not mention auth or rate-limit characteristics, but the conditional-omission detail is genuinely useful beyond the schema.

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, then return semantics, then the conditional-omission caveat. Slightly repetitive in restating 'Fanatics Live show' across sentences, but no sentence is wasted.

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?

For a single-parameter read tool with no output schema and no annotations, the description adequately covers what is returned and when fields are absent. Only missing is any indication of freshness/liveness (it is a 'current state' query) and auth expectations.

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% and the single id parameter is fully documented in the schema (including the cross-reference to /fanaticslive/show/{id}). The main description adds little beyond implying the id refers to a show, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Get a Fanatics Live show's current instant-rip state,' and the second sentence narrows it to 'the current break's digital-instant-rip state.' It is clearly distinguishable from the generic fanaticslive_show, though it never explicitly names or contrasts a sibling.

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

Usage Guidelines3/5

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

Usage is implied by the resource semantics and the conditional 'when a rip is actively in progress,' but there is no explicit when-to-use/when-not and no alternative tool named for related needs (e.g., general show data via fanaticslive_show).

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