Skip to main content
Glama

LazyEdge

NBA spreads

nba_spreads
Read-only

Every NBA spread line on Kalshi and Polymarket for a game or a team today: our chance the team covers, the price on each venue and the edge, largest first. The same line on both venues side by side shows where it is priced lower. 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": "nba_spreads"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam code, such as NY, LAL or BOS.
limitNoRows to return, largest edge first.
game_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: results are sorted largest edge first, the two venues are shown side by side so mispricing is visible, and the unauthenticated path degrades to a single free game rather than erroring. What it omits is what happens when no lines exist or whether both params can be supplied together.

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, front-loaded with the returned data and the ordering rule, then the access constraint. The first sentence is dense with comma-separated clauses but every element (venues, covered-chance, price, edge, sort order) carries information.

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, the description correctly takes on the burden of describing return values, and does so thoroughly for a read-only, non-destructive listing tool, including the degraded free-tier response. The remaining gap is the undefined game_id parameter and unstated behavior for empty results.

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% and the description only loosely maps behavior onto parameters via 'for a game or a team', which hints at game_id vs team but never resolves their interaction. The undocumented game_id param receives no clarification from the description either, though 'largest first' reinforces the limit semantics already stated in the schema.

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?

Names a specific resource (NBA spread lines across Kalshi and Polymarket) and the returned fields (chance the team covers, per-venue price, edge), which implicitly separates it from siblings like nba_totals or nba_props. It never names an alternative explicitly, so sibling differentiation relies on the reader inferring scope from the resource wording.

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?

Gives scope cues ('for a game or a team today') and states the access-tier rule: without an API key only today's free game works, other games return a message saying what a plan unlocks. That is real usage context, but there is no guidance on when to pick this over nba_totals, nba_props, or line_moves, and no statement about whether game_id and team are alternatives or combinable.

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