Skip to main content
Glama
Sign In
sportsdata-mcp

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fanduel_sb_live_score

Read-onlyIdempotent

Retrieve live scores and period state for a FanDuel sportsbook event in New Jersey using its event ID.

Instructions

Live score + period state for one sportsbook event (NJ).

Returns: {openDate, homeTeam:{shortName, abbreviation, score}, awayTeam:{...}, comp, mediaTypes}

Auth: none needed.

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": {
      "eventId": "<eventId>"
    },
    "name": "fanduel_sb_live_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesSportsbook event id (from fanduel_sb_call event_page / content_page). Required — part of the URL path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.24.0
    • addedInput schema / properties / eventId / description
      Added value: +"Sportsbook event id (from fanduel_sb_call event_page / content_page). Required — part of the URL path."
  2. Addedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, and idempotent. The description adds 'Auth: none needed' and specifies the exact return structure (openDate, homeTeam/awayTeam objects, comp, mediaTypes). The 'NJ' restriction is also disclosed. This is useful behavioral context beyond annotations with no contradictions.

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?

Three concise lines: purpose, return shape, and auth. Front-loaded with the most important info. No filler or repetition. Each sentence earns its place.

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 simple tool with strong annotations, the description provides the return shape, auth, and geographic limitation. It doesn't explain period state values or mediaTypes, but that's unnecessary for selection and invocation. The combination of schema, annotations, and description is sufficient.

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?

The input schema has 100% coverage for eventId, including its origin from fanduel_sb_call and URL path requirement. The description itself does not elaborate on the parameter, and the schema already carries the semantic weight. Baseline 3 is appropriate since the schema is sufficient and the description adds no extra parameter nuance.

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?

Description clearly states the tool provides 'Live score + period state for one sportsbook event (NJ)'. This is a specific verb+resource with a geographic scope, distinguishing it from sibling tools like fanduel_sb_call and other sportsbook tools. The 'one event' qualifier directly maps to the eventId parameter.

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?

Use is implied by the purpose: when you need live score for a single sportsbook event. The schema description further guides usage by stating eventId comes from 'fanduel_sb_call event_page / content_page', and the tool description references the return shape. This provides a clear workflow context, though it doesn't explicitly list exclusions or alternatives.

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