Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_leagues

Retrieve Yahoo Sports league catalog keys, namespaces, feature flags, and supported value sets for player search, injuries, drafts, rankings, golf, tennis, and motorsports.

Instructions

Yahoo Sports league catalog. Returns all 24 core league keys, source namespaces, and feature flags, plus the complete supported value sets for player search, injuries, NFL/NBA Draft, college rankings, golf tours, tennis ranking types, and motorsports series. Use dedicated soccer scoreboard, rankings, stats, schedule, bracket, sportsbook, RSS, and dropdown catalogs for live filter values.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It clearly discloses the return payload (core league keys, source namespaces, feature flags, and supported value sets) and scopes out live filter values. It does not explicitly state that the operation is read-only or side-effect-free, but the catalog framing and return-focused language make that behavior strongly implied.

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?

The definition is two sentences with no filler. The primary return content is front-loaded, and the second sentence efficiently handles sibling routing for live filter values.

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

Completeness5/5

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

For a zero-parameter catalog with no output schema, the description supplies the essential return contents and the key usage boundary against live-value catalogs. Nothing needed to invoke the tool correctly is missing.

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 schema is an empty object, so there are no parameter semantics to explain. Baseline for a zero-parameter tool is 4; the description appropriately focuses on output content rather than inventing parameter 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?

The description uses a specific verb ('Returns') and names the exact resource ('Yahoo Sports league catalog'), then enumerates the returned artifacts: 24 core league keys, source namespaces, feature flags, and supported value sets. It distinguishes this catalog from dedicated live-value tools such as soccer scoreboard, rankings, stats, schedule, bracket, sportsbook, RSS, and dropdown catalogs.

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?

It explicitly routes agents away from this tool for live filter values and toward dedicated scoreboard, rankings, stats, schedule, bracket, sportsbook, RSS, and dropdown catalogs. However, it does not explicitly state 'use this tool when you need league keys or static supported value sets'; that use case is strongly implied by the first sentence rather than stated as a direct instruction.

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