Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_game_summary

Retrieve one ESPN game's matchup, betting odds, and boxscore stat totals using sport, league, and event ID.

Instructions

ESPN game summary. Returns one game's matchup, betting odds, and boxscore stat totals. The sport enum accepts football, basketball, baseball, hockey, and soccer. The league enum accepts nfl, college-football, nba, wnba, mens-college-basketball, womens-college-basketball, mlb, nhl, eng.1, esp.1, ita.1, ger.1, fra.1, usa.1, and uefa.champions; it must be valid for the chosen sport. Get an event id from the scoreboard endpoint.

Input Schema

NameRequiredDescriptionDefault
eventYesNumeric ESPN event (game) id
sportYesSport key
leagueYesLeague key (must be valid for the sport)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / league / enum
      Added value: +[
+  "nfl",
+  "college-football",
+  "nba",
+  "wnba",
+  "mens-college-basketball",
+  "womens-college-basketball",
+  "mlb",
+  "nhl",
+  "eng.1",
+  "esp.1",
+  "ita.1",
+  "ger.1",
+  "fra.1",
+  "usa.1",
+  "uefa.champions"
+]
    • addedInput schema / properties / sport / enum
      Added value: +[
+  "football",
+  "basketball",
+  "baseball",
+  "hockey",
+  "soccer"
+]
  2. Addedv1.5.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned content (matchup, odds, boxscore totals), which is useful, but does not cover auth needs, rate limits, error/empty behavior, or explicitly confirm read-only safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description redundantly lists full enum values that are already present in the schema. Those long enum recitations consume space without adding much beyond the schema, though the structure remains clear.

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?

For a three-parameter lookup tool with no output schema and no annotations, the description is nearly complete: it states what is returned, how to obtain the required event id, and the sport-league validity constraint. Minor missing behavioral details keep it from a 5.

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?

Schema coverage is already 100%, so baseline is 3. The description adds real meaning for `event` by explaining that its id comes from the scoreboard endpoint, and reinforces sport/league validity even though the schema already states that constraint.

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 resource and scope: one ESPN game's summary with matchup, betting odds, and boxscore stat totals. It distinguishes itself from the scoreboard by requiring an event id and pointing to the scoreboard only as an id source.

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 gives a clear prerequisite: get the event id from the scoreboard endpoint, and ensure the league is valid for the chosen sport. It does not explicitly name when to use a sibling like espn_scoreboard instead, but the single-game scope and id dependency imply the workflow.

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