Skip to main content
Glama

DeepChamp for Agents

Daily slate

get_daily_slate
Read-onlyIdempotent

Games for a sport and Eastern date with start times, status, and plain-language rest and schedule context. Research intelligence (probabilities, factors, context), not winning picks. Price: Free, no signup. Research and information, not betting advice. No outcomes are guaranteed. Adults 21+ only, where legal. Problem gambling help: 1-800-MY-RESET.

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

Input Schema

NameRequiredDescriptionDefault
dateNoEastern (ET) date, YYYY-MM-DD, from 3 days ago to 7 days ahead. Defaults to today.
sportNoSport. One of nba, nfl, mlb, nhl, cfb, cbb, wnba. Defaults to nba.nba
visualNoOptional. How to present the result: auto (default, chosen by client), image (picture and link), text (terminal chart), none (data only).
harnessNoOptional display hint. It changes the output format only, never access, price or limits.

Output Schema

NameRequiredDescriptionDefault
dataNo
hintNoEmpty day only: the nearest days in the free window that have games (next_games, previous_games).
metaNo
errorNoFailure only: code, message, request_id, billable (false for free tools).
visualNo
billingNo
complianceNo
continue_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Eastern (ET) date, YYYY-MM-DD, from yesterday to tomorrow. Defaults to today."New value: +"Eastern (ET) date, YYYY-MM-DD, from 3 days ago to 7 days ahead. Defaults to today."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "billing": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "compliance": {
      +      "type": "object"
      +    },
      +    "continue_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "data": {
      +      "properties": {
      +        "date": {
      +          "description": "US Eastern calendar date, YYYY-MM-DD.",
      +          "type": "string"
      +        },
      +        "editors_read": {
      +          "type": [
      +            "object",
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "game": {
      +          "description": "get_matchup_context: the game.",
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        },
      +        "game_count": {
      +          "description": "get_daily_slate: games on that day.",
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "games": {
      +          "description": "get_daily_slate: the games, with slug, teams, start time, status, final score and rest.",
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        },
      +        "games_returned": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "position": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "relation": {
      +          "description": "Where the date sits relative to today (yesterday, today, tomorrow or another day).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "schedule": {
      +          "description": "get_daily_slate: start-time window, back-to-back teams, short-rest and rest-gap counts.",
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        },
      +        "sport": {
      +          "type": "string"
      +        },
      +        "teams": {
      +          "description": "get_matchup_context: each team's last result and next game.",
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        },
      +        "timezone": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "total": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "truncated": {
      +          "type": [
      +            "boolean",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "sport",
      +        "date"
      +      ],
      +      "type": "object"
      +    },
      +    "error": {
      +      "description": "Failure only: code, message, request_id, billable (false for free tools).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "hint": {
      +      "description": "Empty day only: the nearest days in the free window that have games (next_games, previous_games).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "meta": {
      +      "type": "object"
      +    },
      +    "visual": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / harness
      Added value: +{
      +  "description": "Optional display hint. It changes the output format only, never access, price or limits.",
      +  "enum": [
      +    "claude-code",
      +    "codex",
      +    "generic"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / visual
      Added value: +{
      +  "description": "Optional. How to present the result: auto (default, chosen by client), image (picture and link), text (terminal chart), none (data only).",
      +  "enum": [
      +    "auto",
      +    "image",
      +    "text",
      +    "none"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is lighter. It still adds real context the annotations do not: free of charge, no signup required, 21+ and legality restrictions, and an explicit caveat that the output is analytical context rather than predictions or outcomes.

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

Conciseness3/5

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

The purpose is correctly front-loaded in the first sentence, but the remainder is a chain of overlapping disclaimers: 'not winning picks', 'Research and information, not betting advice' and 'No outcomes are guaranteed' say largely the same thing three times. Condensing those into one clause would keep the same information at half the length.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile; what remains missing is minor, namely any hint about the visual/harness presentation options. For a read-only listing tool with fully described parameters, the description is sufficient to call it 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% and three of four parameters are enums with documented values, so the schema carries parameter meaning. The description only restates sport and Eastern date and says nothing about the visual or harness display parameters, so it adds no meaning beyond the schema; 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 first sentence names the resource (games), the scoping inputs (sport, Eastern date) and the returned fields (start times, status, rest/schedule context), so an agent knows exactly what it gets. It does not distinguish itself from the sibling get_matchup_context, which is the one remaining ambiguity.

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?

Usage is only implied by the purpose statement: ask for a sport plus a date to get that day's games. There is no explicit when-to-use versus get_matchup_context guidance and no statement of exclusions, so routing between siblings is left to the agent.

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