Skip to main content
Glama

Full line ladder (prematch)

upcoming_lines
Read-onlyIdempotent

Returns the complete ladder of alternate lines for a single market of a single upcoming match, for every period it is offered in (for example every handicap, or every total). Reach for it when the five lines match_prices shows around the main line do not include the number you need, such as a price at one particular handicap. Works on prematch matches only; for in-play matches call match_prices with response_format='detailed'.

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": "upcoming_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesPrematch match id from find_matches with mode='prematch'
market_typeNoThe one market whose lines you wanttotals

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds real behavioral context on top: the result is the complete ladder rather than a sample, it spans every period the market is offered in, and it is restricted to prematch matches. It does not discuss result size, rate limits, or how large ladders behave, which keeps it below 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 sentences, each carrying distinct information: what is returned, the trigger condition relative to match_prices, and the prematch-only constraint with its alternative. The trigger is front-loaded and there is no filler.

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 two-parameter read tool with full schema coverage, no output schema, and annotations covering safety, the description supplies everything an agent needs: the shape of the result, the selection condition, and the in-play exclusion with a redirect. No critical invocation detail is missing.

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 meaning beyond the field descriptions: market_type selects exactly one market, and the returned ladder covers every period that market is offered in — clarifying that no period parameter is needed. The examples (every handicap, every total) also concretize the enum values.

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 — returns the complete ladder of alternate lines for one market of one upcoming match, across every period offered. It distinguishes itself from match_prices by framing itself as the full-ladder counterpart to the five-line sample, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use: reach for it when the five lines match_prices shows around the main line do not include the number you need, e.g. a specific handicap. It also gives an explicit when-not and names the alternative path, telling the agent to call match_prices with response_format='detailed' for in-play matches.

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