Skip to main content
Glama

The Odds Gap

Past Game Result

past_game
Read-onlyIdempotent

A finished game: the final score, the closing spread and total, and the earliest line we recorded, with a link to the game's page. Never an upcoming game.

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": {
      "text": "<text>"
    },
    "name": "past_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoThe game in plain words, for example 'Lions at Bears' or 'Yankees tonight'.
textYesThe team or matchup, in the reader's words.
list_allNoEvery finished game in the window the words name.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the tool produced an answer.
cardNoThe same answer, structured, when there is one. A figure in it keeps its field name (edge_pct, ev_pct) and carries a plain label beside it: "label": "Above Fair" (percent above our fair price, not expected profit) or "Above Break-Even" for a middle.
pageYesThe matching page on theoddsgap.com.
toolNo
as_ofNoWhen the prices were scanned, Eastern Time.
staleNoTrue when that scan is older than usual for our hourly snapshot.
answerYesThe answer in plain sentences.
optionsNoWhen the question could mean more than one thing: whole questions to ask again with.
warningsNo
state_noteNoWhere to check what is legal for you.
decline_kindNoSet when the question is one we do not answer, and which kind.
free_left_todayNo
responsible_gamblingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / card / description
      Previous value: -"The same answer, structured, when there is one."New value: +"The same answer, structured, when there is one. A figure in it keeps its field name (edge_pct, ev_pct) and carries a plain label beside it: \"label\": \"Above Fair\" (percent above our fair price, not expected profit) or \"Above Break-Even\" for a middle."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the boundary that results are always completed games and discloses the returned fields, but says nothing about behavior when the matchup is ambiguous, unfinished, or not found — the cases an agent most needs to anticipate.

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?

A single tight sentence with the exclusion clause front-loaded at the end for emphasis; nothing is padded. It reads as a noun-phrase fragment rather than an action statement, which slightly weakens the opening.

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?

A simple, closed-world read tool with a full schema and an output schema, so return-value detail is not required. The description covers the resource scope and the key boundary condition; only edge-case behavior (no match, multiple matches, in-progress game) is left unstated.

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 all three parameters (game, text, list_all) are already documented in the schema. The description adds no parameter-level meaning — in particular it does not clarify how the plain-word 'game' input relates to the free-form 'text' field or when list_all should be preferred.

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 names the resource precisely (a finished game) and enumerates what comes back: final score, closing spread and total, earliest recorded line, and a link to the game page. The closing constraint 'Never an upcoming game' separates it from upcoming-slate siblings. It stops short of a verb ('retrieve/look up') and never names an alternative tool such as game_lines, so it is clear but not fully differentiated.

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?

'Never an upcoming game' is an explicit when-not condition, which is more than most definitions offer. However, there is no positive when-to-use framing (e.g., 'call this when the reader asks what happened in a completed game') and no named alternative for line-history or upcoming-game queries, leaving the routing decision partly inferred.

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.

Resources