Skip to main content
Glama

LazyEdge

NFL games this week

nfl_games
Read-only

This week's NFL games: our pick and chance, our projected score, the market's chance, our margin and total beside the spread and total lines, and the strongest edge on each game. Without an API key: today's free game only; any other game says what a plan unlocks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this is a safe, closed-world read (readOnlyHint true, destructiveHint false), so the description does not need to re-litigate safety. What it does add is genuine behavioral disclosure beyond annotations: without an API key only today's free game is returned, and other games return a message describing what a plan unlocks, which prevents the agent from misreading a gated response as missing data.

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?

Two sentences, no filler, and the returned-metrics list is front-loaded before the access caveat. The first sentence is long and comma-heavy, but each clause names a distinct output field rather than padding, so the density is justified.

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?

With no output schema present, the description carries the burden of explaining returns, and it does so concretely by naming each metric and the edge summary. The auth-tier behavior is also covered. Minor gaps remain: it does not say how 'this week' is defined at week boundaries or how fresh the projections are.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not waste words inventing parameter guidance for a parameterless call.

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 a specific resource (this week's NFL games) and enumerates exactly what each entry carries: pick and win chance, projected score, market chance, model margin/total versus the spread and total lines, plus the strongest edge. That is far more specific than the title alone. It stops short of explicitly distinguishing itself from siblings like nfl_props or nfl_prop_pairs, leaving the agent to infer that this is the game-level slate rather than player props.

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: an agent can infer it should call this to get the current week's slate, and the access note implies you may still want it without a key. There is no explicit when-to-use framing, no statement of what it does not cover (player props, historical weeks), and no routing to alternatives such as nfl_props or results.

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