Skip to main content
Glama

LazyEdge

Today's free game

free_game
Read-only

Today's free game, open to everyone without a key: the league, the matchup, the start time, our number on it now with the time it was produced and whether it is pregame or live, how far it has moved since the start, and which tools open the rest of it. Call this first without a key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive status, but the description adds substantive context they don't: no key is required, the response carries a production timestamp (freshness/staleness signal), and it distinguishes pregame from live data. It does not explain behavior when no game is scheduled, which is the remaining gap.

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?

Everything is packed into one front-loaded sentence that starts with the resource and the key constraint (free, no key). It is comma-dense and the phrase "our number on it now with the time it was produced" reads awkwardly, but no sentence is wasted.

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 zero-parameter tool with no output schema, the description does the heavy lifting by listing the returned fields and pointing to tools that cover the remainder. The only omission is behavior on days with no game and any hint about output format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This tool takes zero parameters, so per the baseline there is no parameter meaning for the description to supply. The schema's empty object is consistent with the description's framing as a parameterless entry point.

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 names a specific resource (today's free game) and enumerates exactly what it returns: league, matchup, start time, current number with production timestamp, pregame/live status, and line movement since open. That payload inventory distinguishes it from the surrounding props/spreads/results tools without needing to name them.

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?

"Call this first without a key" is explicit sequencing guidance and tells the agent no authentication is needed, which is the key decision point. It stops short of naming concrete alternatives or stating when not to call it, but the "which tools open the rest of it" phrasing makes its role as entry point clear.

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