Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_injury_report

Fetch Yahoo Sports injury tables for NFL, NBA, MLB, or NHL by league or team to check player status, injury descriptions, and start dates.

Instructions

Yahoo Sports injury report. Returns Yahoo's current injury table for NFL, NBA, MLB, or NHL. Omit team_id for the page's All Teams view, or provide a Yahoo team ID from yahoo-sports-dropdown-catalog. Each injury row preserves Yahoo's player, position, status, injury description, and start date.

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

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague with an injury page
team_idNoOptional Yahoo team ID from yahoo-sports-dropdown-catalog; omit for All Teams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the behavioral burden. It clearly describes a read operation, states the league scope and All Teams behavior, and lists the injury row fields returned. It does not mention pagination or rate limits, but for a simple current-injury-table read it discloses the key behavior.

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 description is three compact sentences, front-loaded with the core purpose and followed by filtering and return-field details. Every sentence adds useful information without repetition.

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?

There is no output schema or annotation coverage, but the description still covers the essential scope: supported leagues, team filtering, All Teams behavior, and the fields present in each injury row. That is enough for an agent to call and interpret this simple read tool correctly.

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%, so both parameters are already documented in the schema. The description restates the team_id behavior and league coverage, but adds no parameter meaning beyond what the schema provides; baseline 3 is appropriate.

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 and resource: it returns Yahoo's current injury table for four named leagues. This is clearly distinct from sibling tools like yahoo_sports_player, yahoo_sports_team_roster, or yahoo_sports_news.

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 explains how to use the optional team_id: omit it for the All Teams view, or supply a Yahoo team ID from yahoo-sports-dropdown-catalog. It does not explicitly compare this tool to alternatives, but the injury-table scope provides clear usage context.

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