Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_sports_stats_discovery

Read-only

Return one league/page type's current stats tabs, filters, filter values, and sortStatIds. Use these values with yahoo_sports_stats; start with yahoo_sports_stats_catalog to find supported pages.

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": {
      "league": "<league>"
    },
    "name": "yahoo_sports_stats_discovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueYesRequired. Stats category from yahoo-sports-stats-catalog.
page_typeNoOptional. Stats template; defaults to individual.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the dependency chain (catalog -> discovery -> stats) and that the returned payload is metadata (tabs/filters/sortStatIds) rather than actual stats. It does not mention pagination or rate limits, but this is a small parameter-less lookup where that is unlikely to matter.

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?

Two sentences, both load-bearing: the first declares the output, the second declares the workflow position. No filler.

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 an output schema present and annotations covering safety, the description only needs to supply workflow context, which it does. Minor gap: it does not clarify whether page_type accepts multiple values or how to discover valid page types, which an agent must resolve from the catalog tool.

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% — the league parameter already states it is required and comes from yahoo-sports-stats-catalog, and page_type already documents its default. The description's "one league/page type's" mirrors rather than extends that, so this sits at the baseline for a fully-documented two-parameter schema.

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 concrete verb ("Return") plus the exact artifacts produced: current stats tabs, filters, filter values, and sortStatIds for one league/page type. It also names the two adjacent tools (yahoo_sports_stats, yahoo_sports_stats_catalog), so an agent can place it precisely in the workflow without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit call order: start with yahoo_sports_stats_catalog to find supported pages, then call this, then feed the returned values into yahoo_sports_stats. Both the prerequisite and the downstream consumer are named, leaving no ambiguity about when this tool is the right one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources