Skip to main content
Glama

Prices for a single match

match_prices
Read-onlyIdempotent

Fetches the latest Pinnacle quotes for one match: moneyline, handicaps (spreads) and over/unders (totals), plus team totals if you include them in markets, for each period you list. Period 0 means the whole game; 1 is the first half or first period, 2 the second, etc. In concise form each handicap/total market is cut to the five lines around the main line; detailed returns the full ladder. Take event_id from find_matches or price_moves, and use the same mode you found it under, because in-play and prematch matches sit on separate boards. Prices are fetched fresh; each call counts as one request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "match_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoBoard the id belongs to: 'live' or 'prematch'live
marketsNoWhich markets to include
periodsNoPeriod numbers; 0 is the full game
event_idYesMatch id returned by find_matches or price_moves
response_formatNo'concise' trims each ladder to five lines around the main line; 'detailed' returns all of themconcise

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing freshness ('Prices are fetched fresh') and a per-call cost ('each call counts as one request'), which matters for an open-world network tool. It also explains the concise-mode trimming rule (five lines around the main line) so the agent understands the shape of what comes back.

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?

Purpose and payload come first, then the period/market semantics, then the concise/detailed trade-off, then id sourcing and cost. Every sentence carries information an agent would otherwise have to guess, and nothing is repeated from the schema or annotations.

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

Completeness5/5

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

For a five-parameter read-only tool with no output schema and full schema coverage, the description supplies everything needed: what is returned, how periods and modes work, how to obtain a valid id, how verbosity is controlled, and that each call has a request cost.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it decodes the `periods` integers (0 = whole game, 1 = first half/period, 2 = second, etc.), explains the `markets` team-total option, and spells out the concise vs detailed ladder effect. It does not add anything for `event_id` beyond the schema, but the period and mode semantics are genuine value.

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?

States a specific verb and resource ('Fetches the latest Pinnacle quotes for one match') and enumerates exactly what is returned: moneyline, handicaps, over/unders, and optional team totals per period. An agent can tell this apart from find_matches (id discovery) and price_moves (movement) without opening any schema.

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?

Gives concrete prerequisites: take event_id from find_matches or price_moves, and reuse the same `mode` because in-play and prematch matches live on separate boards. It stops short of naming when a different sibling (e.g. upcoming_lines or board_sports) would be the better choice, so it is clear context rather than explicit when/when-not routing.

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