Skip to main content
Glama
Sign In
sportsdata-mcp

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

entain_event_market_rules

Read-onlyIdempotent

Look up settlement rules for named markets by rule ID to clarify how outcomes are graded.

Instructions

Settlement rules for every named market, indexed by rule id.

Returns: {market_rules:{<rule_id>:{id, name, description}}}

Auth: works without a key; ENTAIN_REFRESH_TOKEN unlocks more if set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "entain_event_market_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark it read-only, open-world, and idempotent. The description adds useful context beyond annotations by specifying the return shape and clarifying auth behavior—keyless access with optional deeper access via ENTAIN_REFRESH_TOKEN.

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 compact lines: scope, return shape, auth. Each sentence carries distinct information with no filler, and the most important statement is front-loaded.

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?

For a no-input, no-output-schema read-only call, the description is complete: it states what is returned, the structure, and authentication requirements. Nothing an agent needs to invoke it correctly is missing.

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?

With zero parameters, the schema cannot be ambiguous and the description doesn't need to document inputs. It still helps by noting that results are indexed by rule id, which explains how a caller references returned rules.

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?

The description identifies a distinct resource—settlement rules for named markets, indexed by rule id—which separates it from sibling tools like entain_event_market_type_groups. It lacks an explicit verb like 'get' or 'retrieve', but the intent is unambiguous.

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 first sentence implies the use case: consult this tool when settlement rules by rule id are needed. However, it names no alternatives or when-not-to-use conditions, leaving an agent to infer which sibling tools might be more appropriate.

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