Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticslive_shops

Fetch Fanatics Live's public shop directory to retrieve each shop's ID, name, slug, logo, and follower count. Use the returned slug directly with /fanaticslive/shop/{slug}.

Instructions

Get Fanatics Live's shop directory. Returns Fanatics Live's full public shop directory: every shop's id, name, slug, logo, and follower count. Each entry's slug is usable directly with /fanaticslive/shop/{slug}. Public data sourced from Fanatics Live's own GraphQL API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses that the data is public, sourced from Fanatics Live's GraphQL API, and that it returns the full directory with every shop's fields. It does not cover rate limits or caching, but for a read-only public directory this is sufficient.

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?

Three sentences deliver the purpose, return fields, and a usage pointer with no fluff. The first sentence is slightly redundant with the tool name, but the subsequent details justify its inclusion.

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 zero-parameter, read-only directory tool, the description explains the output fields and the integration path for the slug. It does not mention the exact response envelope (e.g., array vs object), but 'every shop's id...' sufficiently implies a collection of shop objects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the empty input schema is fully documented (100% coverage). Baseline for 0 params is 4; the description does not need to add parameter-level detail.

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 ('Get') and resource ('Fanatics Live's shop directory'), then details the exact return fields (id, name, slug, logo, follower count). The implied contrast with sibling fanaticslive_shop is clear from the phrase 'full public shop directory' and the slug path provided.

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?

Provides clear context: this returns the full directory and that each slug can be used with /fanaticslive/shop/{slug}. It does not explicitly name alternatives or state when not to use this tool, but the pointer to the shop endpoint gives the agent the next step.

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