Skip to main content
Glama
Sign In
sportsdata-mcp

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

betr_master_category

Read-onlyIdempotent

Retrieve master categories and competitions for a specified event type, with optional levelled markets and class filters, to structure sports odds comparison.

Instructions

Master categories (competitions) for one event type, optionally with levelled markets.

Returns: {EventTypeDesc, EventTypeId, MasterCategories:[{MasterCategoryId, MasterCategory, Categories:[{CategoryId, CategoryName}]}]}

Example: Basketball competitions {"EventTypeId": 107}

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": {
      "EventTypeId": "<EventTypeId>"
    },
    "name": "betr_master_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
EventTypeIdYesEvent type id (e.g. 107 Basketball, 1 Racing).
EventClassCodeNoOptional class filter, e.g. "FEATURERACE" for racing.
WithLevelledMarketsNoInclude levelled markets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.24.0
    • addedInput schema / properties / EventClassCode / description
      Added value: +"Optional class filter, e.g. \"FEATURERACE\" for racing."
    • addedInput schema / properties / EventTypeId / description
      Added value: +"Event type id (e.g. 107 Basketball, 1 Racing)."
    • addedInput schema / properties / WithLevelledMarkets / description
      Added value: +"Include levelled markets."
  2. Addedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds meaningful context beyond annotations: it explicitly states 'Auth: none needed' and provides the exact return shape. It does not contradict annotations and covers the key behavioral aspects relevant for safe invocation.

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 compact and front-loaded: a one-line purpose, a Returns block, and a brief example. Every sentence adds value, no redundancy, and the structure is easy to scan.

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?

Despite the lack of an output schema, the Returns block fully documents the nested response structure, and the example clarifies usage. Combined with complete parameter schemas and annotations, the description provides everything an agent needs to invoke the 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 each parameter is already documented. The description adds a concrete example using EventTypeId 107 and mentions 'optionally with levelled markets', but does not add significant semantics for EventClassCode or WithLevelledMarkets beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool provides master categories for an event type, optionally with levelled markets, and includes a return structure. It is clear but does not use a specific verb like 'get' or 'list' and does not explicitly differentiate from closely related siblings such as betr_master_event or betr_sports_category.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given on when to use this tool versus alternatives. The example shows a valid parameter (EventTypeId 107) but does not provide context such as 'use this for top-level categories' or 'prefer this over betr_sports_category when...'.

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