Skip to main content
Glama

Sports Game Odds (Unofficial)

Sgo Events

sgo_events
Read-onlyIdempotent

List upcoming games with odds. Returns scheduled events for a league (NFL, NBA, MLB, NHL, EPL, etc.) with team names, start time, status, and eventIDs to fetch full odds. Example: sgo_events({ leagueID: "NFL", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-sports-game-odds-api-key",
      "leagueID": "NFL"
    },
    "name": "sgo_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesSports Game Odds API key (get one free at sportsgameodds.com, Amateur plan).
leagueIDYesLeague identifier, e.g. "NFL", "NBA", "MLB", "NHL", "EPL", "BUNDESLIGA". Comma-separate for multiple.
oddsAvailableNoOnly return events that currently have odds available. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Sports Game Odds API key (get one free at sportsgameodds.com — Amateur plan)."New value: +"Sports Game Odds API key (get one free at sportsgameodds.com, Amateur plan)."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-sports-game-odds-api-key",
      +    "leagueID": "NFL"
      +  },
      +  {
      +    "_apiKey": "your-sports-game-odds-api-key",
      +    "leagueID": "NBA,MLB",
      +    "oddsAvailable": true
      +  }
      +]
  3. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "_apiKey": "your-sports-game-odds-api-key",
      -    "leagueID": "NFL"
      -  },
      -  {
      -    "_apiKey": "your-sports-game-odds-api-key",
      -    "leagueID": "NBA,MLB",
      -    "oddsAvailable": true
      -  }
      -]
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-sports-game-odds-api-key",
      +    "leagueID": "NFL"
      +  },
      +  {
      +    "_apiKey": "your-sports-game-odds-api-key",
      +    "leagueID": "NBA,MLB",
      +    "oddsAvailable": true
      +  }
      +]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without description help. The description adds the shape of what comes back (teams, start time, status, eventIDs), which is genuinely useful. It says nothing about result volume, pagination, or how fresh/upcoming the schedule window is, which matters for an open-world data feed.

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

Conciseness4/5

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

Three tight sentences: purpose, return fields, then a concrete example — front-loaded and waste-free. The stray '<league>' placeholder in the opening line is a minor blemish that reads as an unfilled template token.

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 read-only listing tool with a fully described schema, rich annotations, and no output schema, the description covers purpose, scope, and return fields adequately. The remaining gap is pagination/result-cap behavior, which is low-risk for this complexity level.

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 league identifiers, comma-separation, and the oddsAvailable default are fully documented in the schema itself. The description reinforces this with a worked example call, but adds no semantics beyond it (e.g. case sensitivity, valid league list boundaries, what oddsAvailable=false yields). Baseline 3 applies.

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 gives a specific verb and resource ('List upcoming games', 'Returns scheduled events for a league') and enumerates the return fields: team names, start time, status, eventIDs. It signals the hand-off to a separate odds-fetching step, which differentiates it from the odds sibling, but it never names that sibling explicitly, leaving the distinction to inference.

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?

Usage context is clear: this is the discovery step for a league's schedule, and the eventIDs it returns are the input for fetching full odds. That gives an implied workflow ordering. It stops short of explicit when-not guidance or naming the alternative tool for odds.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.