Skip to main content
Glama

NegativeEV bet checker

Today's slate

get_slate
Read-only

Which of MLB, WNBA, PGA, ATP, and NFL have a checkable slate right now - at least one simulated game that has not started. Pass sport for one; omit it for all. Free, spends no check. It is not required before check_bet, which reports a missing slate itself at no cost. Call it to answer "what can be checked today", or after a no_slate or ungraded result, which mean the game is not on the simulated slate rather than that the bet was worded wrong.

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_slate"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoOne of: MLB, WNBA, PGA, ATP, NFL. Omit to get every live sport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sport / description
      Previous value: -"One of: MLB, WNBA, PGA, ATP. Omit to get every live sport."New value: +"One of: MLB, WNBA, PGA, ATP, NFL. Omit to get every live sport."
    • changedInput schema / properties / sport / enum
      Previous value: -[
      -  "MLB",
      -  "WNBA",
      -  "PGA",
      -  "ATP"
      -]New value: +[
      +  "MLB",
      +  "WNBA",
      +  "PGA",
      +  "ATP",
      +  "NFL"
      +]
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changed
    • changedInput schema / properties / sport / description
      Previous value: -"One of: MLB, WNBA, ATP. Omit to get every live sport."New value: +"One of: MLB, WNBA, PGA, ATP. Omit to get every live sport."
    • addedInput schema / properties / sport / enum
      Added value: +[
      +  "MLB",
      +  "WNBA",
      +  "PGA",
      +  "ATP"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / sport / description
      Previous value: -"One of: MLB, WNBA. Omit to get every live sport."New value: +"One of: MLB, WNBA, ATP. Omit to get every live sport."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint already declares this a safe read, but the description adds real behavioral context beyond annotations: it is free and spends no check, and it clarifies that no_slate/ungraded means the game is absent from the simulated slate rather than a wording error. It stops short of describing the response shape or how multiple sports are returned.

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 scope-defining sentence is front-loaded and each following sentence carries separate value (cost, non-prerequisite, interpretation of no_slate). It is dense but the final clause is slightly run-on and could be split for faster scanning.

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 one-optional-parameter read-only tool with no output schema, the definition covers purpose, cost, prerequisite status, and error interpretation. What it omits is only the shape of the result (e.g., a list of qualifying sports), which is a minor gap given the simplicity of the 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 coverage is 100%, and the schema itself already documents the enum and that omission returns every live sport. The description's 'pass sport for one; omit it for all' restates that without adding format, case, or default behavior beyond the schema, so baseline 3 applies.

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 query — which of five named leagues currently have a checkable slate — and defines the qualifying condition (at least one simulated game not yet started). An agent can distinguish it from check_bet and get_usage without reading any 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 call contexts ('what can be checked today', or after a no_slate/ungraded result) and an explicit non-requirement, noting it need not precede check_bet because that tool self-reports a missing slate. Both the when and the when-not are stated.

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.