Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_sports_draft

Read-only

Fetch NFL or NBA Draft results, mock, big-board, or news pages. Use the league and view values shown in Yahoo's Draft navigation to select a page.

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_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoOptional NFL or NBA draft page variant from the tabs in this response: results, mock, big-board, or news. Defaults to results.
leagueYesRequired Yahoo draft league; use nfl or nba and check draft=true in yahoo-sports-leagues.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe external read. The description adds that it returns pre-built pages rather than query results and that valid values come from the site's own navigation, but it says nothing about pagination, caching, or failure behavior on bad league/view values.

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, zero filler, with the operation and its return scope front-loaded before the selection hint. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and the two parameters are fully covered by the schema plus the description. The only gap is the absence of an explicit alternative-tool routing statement, which is minor for a narrow two-parameter page fetcher.

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%: both `league` (nfl/nba, must be draft=true in yahoo-sports-leagues) and `view` (results/mock/big-board/news, defaults to results) are fully documented in the schema. The description only echoes those values, so 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 (Fetch) and enumerates the exact resources it returns: NFL/NBA draft results, mock, big-board, and news pages. That is far more concrete than a generic 'get draft data'. It does not, however, distinguish itself from neighboring yahoo_sports_* tools such as yahoo_sports_news or yahoo_sports_leagues beyond the implicit 'draft' scoping.

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 second sentence gives a concrete selection rule: use the league and view values as shown in Yahoo's Draft navigation, and the schema points at yahoo-sports-leagues with draft=true as the prerequisite. That is useful implied usage, but there is no explicit statement of when to prefer this over other Yahoo Sports tools or what happens with an invalid league.

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