Skip to main content
Glama

get_betrivers_markets

Read-only

Read native BetRivers US-PA pregame priced markets. League NBA(default),NFL,NHL or native event_id, not both; market_id requires event_id. Explicit betrivers grant and selected bookmaker required. Independent native decimal/American prices, changedDate clocks, partial capture, no settlement or cross-book equivalence.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
leagueNo
offsetNo
event_idNo
market_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, open-world), and the description adds real value on top: an authorization prerequisite, independent native prices in decimal/American, changedDate clocks, partial capture, and no settlement or cross-book equivalence. What it does not do is unpack those terse caveats, for example what 'partial capture' means in practice or how results are paginated.

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?

The description is short and front-loaded, with the resource identified before constraints and caveats, and no filler sentences. The telegraphic compression ('changedDate clocks', 'partial capture') costs a little readability but wastes no space.

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?

There is no output schema, so the description is the only source for return semantics, and it covers price format and the absence of settlement/cross-book equivalence reasonably well. However, it never mentions paging behavior for limit/offset (with a max offset of 5000) and its league list is narrower than the schema enum, both of which matter for correct invocation.

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%, so the description carries the full burden, and it only partially does so. It explains the league/event_id exclusivity and the market_id dependency, but omits limit and offset entirely and lists only NBA/NFL/NHL while the schema enum allows NCAAF, NCAAB, EPL, MLS, and UCL, leaving an agent to guess whether those values work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Read) and a precisely scoped resource (native BetRivers US-PA pregame priced markets), which immediately separates it from siblings like get_fanduel_markets, get_pinnacle_markets, and get_markets. The 'native' and 'pregame' qualifiers tell an agent this is single-book, pre-match data rather than an aggregated or live feed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete selection rules: query by league (NBA by default) or by native event_id but not both, and market_id requires event_id. It also states the prerequisites (explicit betrivers grant and a selected bookmaker). It stops short of naming an alternative tool to use when no grant exists or when cross-book comparison is wanted, which keeps it from a 5.

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.