Skip to main content
Glama

get_novig_markets

Read-only

Read Novig exchange pregame prices: moneyline, spread, total, team total and player props, with the ask (the price a taker gets) in American and decimal odds, the bid, and the no-vig fair price. is_main marks the most balanced strike; alternates=true returns every strike. Available to every 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": "get_novig_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
leagueNoNFL
marketNo
offsetNo
playerNo
event_idNo
alternatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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), so the description's job is added context, and it delivers: it specifies the returned price fields (ask in both American and decimal, bid, no-vig fair price), explains is_main semantics, and states that 'Available to every key'. It omits pagination/limit behavior and what happens when no strikes match, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with no filler: the resource and market coverage come first, then the return contents, then the strike-selection semantics and access note. Every clause carries information an agent would otherwise have to guess.

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?

For a 7-parameter tool with no output schema, the description does unusually well on the return side, describing the price fields directly instead of relying on a schema that does not exist. The parameter side is the gap: with zero schema coverage, most arguments are uninterpretable from the definition alone.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description carries the full burden and only partly meets it: it explains alternates=true ('returns every strike') and implicitly maps market to the enumerated market types. limit, offset, league, player, and event_id — including their formats and defaults — are left entirely undocumented anywhere.

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 states a specific verb and resource ('Read Novig exchange pregame prices') and enumerates the market types covered, which lets an agent distinguish it from the BetRivers/FanDuel/Pinnacle siblings by book and from live tools by the 'pregame' scope. It never explicitly contrasts itself with the generic get_markets, so the differentiation is inferential rather than stated.

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 by the resource description (pregame prices on Novig, any market type), and 'Available to every key' usefully signals there is no entitlement gating. However there is no explicit when-to-use versus the generic market tools, no statement of when to prefer it, and no exclusions or error conditions.

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.