Skip to main content
Glama

LazyEdge

Graded record

results
Read-only

How our numbers have graded: an NBA night or NFL week (the newest by default), each finished game with our pregame call on the winner, the spread and the total and whether it was right, and the season totals against the market. Free 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": "results"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoAn NBA night, YYYY-MM-DD (newest when left out).
weekNoAn NFL week this season (newest when left out).
sportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish this as a safe, closed, read-only operation, so the description's job is to add context — and it does: newest-by-default behavior, that only finished games are included, what verdicts and season totals are reported, and that no API key is required. It stops short of noting any result limits or pagination, which keeps it from a 5.

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?

A single front-loaded sentence opens with the core purpose and then enumerates the returned content without filler. It is dense and slightly run-on, but every clause carries information and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does a fair job sketching the return contents (per-game calls plus season totals). However, the three-way interaction among date, week, and sport is left ambiguous, which is the main thing an agent needs to invoke this tool 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 coverage is 67%, so the bar is moderate. The description adds the useful default rule ('the newest by default') and ties date to NBA nights and week to NFL weeks, but it never explains the sport enum or how sport interacts with date/week (e.g., whether sport is required to disambiguate or is inferred). That leaves a real semantic gap the schema does not close.

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 gives a clear verb-and-resource picture: it returns how the site's predictions 'graded' for finished games, per game and as season totals against the market. It implicitly separates itself from nba_games/nfl_games by stressing finished games with pregame calls and hit/miss verdicts, though it never names those siblings to make the contrast explicit.

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 implied rather than stated: you use this to review past performance, defaulting to the newest NBA night or NFL week. There is no explicit when-to-use versus the schedule tools (nba_games, nfl_games) and no statement about what happens if you supply neither, both, or an unsupported combination of date/week/sport.

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