Skip to main content
Glama

Tonight Slate & Live Scores

tonight_slate
Read-onlyIdempotent

Use this when the user asks what is on tonight, today's scores, or a given day's games ('NBA games on 2026-11-05'). Returns that day's games with game_id, teams (id and abbreviation), times (US Eastern), live or final scores, pre-game win probabilities (NBA: our projection, blended with the market while the model learns) and the consensus line (signed in: the market's chance and the model's edge), last-game starters (NBA) and recent injury status changes; each game's page is game_url with its id in place of {id}. Not for a game weeks away or one team's schedule: use find_game.

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": "tonight_slate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date in YYYY-MM-DD format. Omit for the current/next slate with injury changes.
leagueNoLeague ("nba" or "nfl").nba

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description is free to spend its budget on data semantics — and it does: US Eastern times, live vs final score states, and that NBA win probabilities are a projection blended with the market while the model learns. It also flags that the consensus line's market chance/model edge is only shown 'signed in', which is a real access condition. Minor deduction because that sign-in condition is stated cryptically and the blending behavior's effect on the returned number is not fully spelled out.

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?

Front-loaded with the selection trigger, then the return payload, then the routing exclusion — a sensible order. The middle clause is a long parenthetical-laden run-on enumerating return fields, which is dense but each item is substantive rather than filler.

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?

There is no output schema, so the description correctly carries the full return-value burden: it enumerates the fields, specifies the times' timezone, distinguishes live from final scores, and explains the game_url/{id} templating. Combined with the explicit alternative tool for out-of-scope requests, an agent has everything needed to call and interpret this tool.

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%, with the date format, the omit-for-current-slate behavior, and the league enum already documented in the schema. The description echoes the date-format usage through its example and adds the US Eastern timezone convention for the output, but contributes little new meaning about the two parameters themselves. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb-and-resource pair: returns a given day's slate of games with a concrete field inventory (game_id, teams, times, scores, win probabilities, consensus line, starters, injuries). It explicitly separates itself from find_game by naming the cases it does not cover ('a game weeks away or one team's schedule'), so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit trigger phrasing ('what is on tonight, today's scores, or a given day's games') plus a concrete date example, and then an explicit exclusion with the alternative tool named for each excluded case. Nothing about when to select this over find_game is left to inference.

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