Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_stats_discovery

Discover Yahoo Sports stats page tab IDs, filter parameters, and sort-stat IDs for a league, so you can build valid stats queries for selectedTable, week, position, and more.

Instructions

Yahoo Sports stats tabs and filters. Returns the live tab ids, filter parameters and values, and sort-stat ids for one Yahoo league stats page. This is the discovery surface for selectedTable, qualified, leagueStructure, positionIds, cutTypeIds, sortStatId, week, and weekSeasonPhase.

Input Schema

NameRequiredDescriptionDefault
leagueYesStats league key
pageTypeNoStats page type; defaults to individual

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return payload (tab ids, filter parameters and values, sort-stat ids), which is the key trait for a discovery tool, and 'live' signals values are fetched at call time. It omits stability/caching, whether results vary by season or week, and any failure modes for unsupported league/pageType combinations.

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 short sentences, front-loaded with the resource and immediately followed by the return payload. The opening fragment 'Yahoo Sports stats tabs and filters' is slightly clipped but not wasteful; every sentence contributes.

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?

With no output schema, the description must describe the return shape, and it does so concretely by naming the ids and filter values returned. The downstream field list (selectedTable, positionIds, cutTypeIds, etc.) tells the agent what these values feed into. Only the league/pageType-specific variation and sibling hand-off are missing.

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 both parameters are enumerated, so the schema fully documents league and pageType. The description adds no meaning beyond that — it never explains how pageType (individual/weekly/team) changes the returned tab set, which would have been genuinely additive information.

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 resource (Yahoo league stats page tabs/filters) and what it returns: live tab ids, filter parameters and values, sort-stat ids. It is clearly a discovery/metadata tool rather than a data-fetch tool. However, it never names or contrasts with the nearby siblings yahoo_sports_stats and yahoo_sports_stats_catalog, leaving the agent to infer the division of labor from names alone.

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?

The phrase 'This is the discovery surface for selectedTable, qualified, ... sortStatId, week, weekSeasonPhase' implies it should be called before fetching stats, which is useful implicit guidance. But there is no explicit when-to-use statement, no prerequisite ordering ('call this first, then pass ids to yahoo_sports_stats'), and no exclusion for the catalog sibling.

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