Skip to main content
Glama

get_pinnacle_markets

Read-only

Read Pinnacle pregame prices (international book, not US-licensed): moneyline, spread, total, team total and specials (player props, futures and other Pinnacle specials with their native category) for NFL, NCAAF, NBA, NCAAB, NHL, EPL, MLS, UCL and Bundesliga. Available to every key. Read through at request time (reused up to 20 seconds); no Pinnacle history is stored.

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_pinnacle_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
leagueNoNFL
marketNo
offsetNo
alternatesNo
matchup_idNo

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 cover read-only/open-world/non-destructive safety, and the description adds real context beyond them: the book is international and not US-licensed, results are read through at request time and cached up to 20 seconds, and no Pinnacle history is stored (implying historical lookups need another tool). It stops short of describing the response shape or pagination behavior.

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 dense sentences, front-loaded with the book and market scope before the operational caveats. The parentheticals are informative rather than filler, though the list of leagues and specials is long enough to make the first sentence heavy.

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 six-parameter, no-output-schema read tool with zero schema descriptions, the description covers scope and freshness well but leaves the four non-enum parameters (limit, offset, alternates, matchup_id) and the return shape undocumented. An agent can call it with defaults but cannot confidently use alternates or matchup_id filtering.

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 description coverage is 0%, and the description only partially compensates: the market-type enumeration maps onto the 'market' enum and 'specials ... with their native category' clarifies what 'special' returns. The league list matches the enum. But limit, offset, alternates (which likely changes spread/total lines materially), and matchup_id receive no explanation 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 opens with a specific verb and resource ('Read Pinnacle pregame prices') and enumerates the market types (moneyline, spread, total, team total, specials) and the nine covered leagues. The book name ('Pinnacle, international, not US-licensed') is what separates it from the FanDuel/BetRivers siblings, though no sibling is named explicitly.

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?

'Pregame' implicitly signals this is not for in-play pricing, and 'available to every key' tells the agent there is no permission gate. However, there is no explicit when-to-use versus get_live_events, get_player_props, or get_history, and no statement of when to prefer the generic market tools.

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.