Skip to main content
Glama

Sports Game Odds (Unofficial)

Sgo Event Odds

sgo_event_odds
Read-onlyIdempotent

Get all odds & player props for a specific game. Returns moneyline, spread, and total markets plus player props for a single event, with prices across sportsbooks. Look up the eventID first via sgo_events. Example: sgo_event_odds({ eventID: "abc123", _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",
      "eventID": "abc123"
    },
    "name": "sgo_event_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesSports Game Odds API key (get one free at sportsgameodds.com, Amateur plan).
eventIDYesEvent identifier, from sgo_events (event.eventID).

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",
      +    "eventID": "abc123"
      +  }
      +]
  3. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "_apiKey": "your-sports-game-odds-api-key",
      -    "eventID": "abc123"
      -  }
      -]
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-sports-game-odds-api-key",
      +    "eventID": "abc123"
      +  }
      +]
  5. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered by structured fields. The description adds useful context about what comes back (multiple market types plus sportsbook-level pricing), which matters because there is no output schema. It says nothing about rate limits, API-key failure modes, or how missing markets are represented, so it adds only partial behavioral context.

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?

The return contents are front-loaded in the first two sentences and the prerequisite follows, so an agent gets the important facts immediately. The trailing inline example largely duplicates the schema's own 'examples' block and is the one element that does not fully earn its space.

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?

With no output schema, the description needs to convey the shape of the response, and it does so by naming the market types and cross-book pricing. The prerequisite chain to sgo_events and the API-key requirement are both covered, leaving only minor gaps such as error or empty-market behavior.

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 both eventID and _apiKey are already documented in the schema, including that eventID comes from sgo_events. The description reinforces the eventID provenance but adds no format, casing, or validity rules beyond what the schema states. Baseline 3 is appropriate when the schema carries the parameter burden.

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 verb and resource ('Get all odds & player props for a specific game') and enumerates the exact market types returned (moneyline, spread, total, player props). It also implicitly separates itself from the sibling sgo_events, which is named as the event-lookup step rather than the odds 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 states the required prerequisite workflow explicitly: 'Look up the eventID first via sgo_events,' which routes the agent to the correct sibling before calling this tool. It does not state any when-not-to-use conditions or limits on how many events can be queried at once, which keeps it short of a 5.

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.