Skip to main content
Glama
Sign In

YorkerAPI

by io.github.noahowsh
OverviewDiscussionsAdmin

Line movement

get_line_movement
Read-onlyIdempotent

Use for how one match's market moved: every pregame snapshot by sportsbook (decimal and American), the median margin-free probability per snapshot, and with include_in_play the prices taken during the match. Costs 10 credits. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

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": {
      "match_id": "<match_id>"
    },
    "name": "get_line_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to cricket. One of: cricket, test, odi, t20i, ipl, bbl, psl, cpl, blast, hundred, sa20, ilt20, county, wbbl, wpl, hundred_women.
match_idYesMatch id from get_matches.
bookmakerNoOne book's key, e.g. "pinnacle".
include_in_playNo

Output Schema

NameRequiredDescriptionDefault
countYes
in_playYes
pregameYes
match_idYes
consensusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds genuinely new operational facts: a concrete cost of 10 credits and the exact output shapes (dual price formats and median margin-free probability). It also discloses a hard usage constraint about not computing stakes/payouts or recommending bets, which annotations cannot express.

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 tight sentences, front-loaded with the use case, then cost/output, then the compliance constraint. Every clause carries information an agent needs; nothing is redundant with the 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?

Given four parameters, an output schema, and full annotation coverage, the remaining gaps an agent would care about — cost and the meaning of the undocumented include_in_play flag — are both addressed. Nothing needed to call this correctly 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 75%, and include_in_play has no schema description at all — the description fills that gap by defining it as prices taken during the match. It also scopes bookmaker to 'every pregame snapshot by sportsbook', clarifying that this is a filter rather than a requirement.

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 ('how one match's market moved') and enumerates exactly what comes back: every pregame snapshot per sportsbook in both decimal and American, plus the median margin-free probability per snapshot. That snapshot-history framing is enough to distinguish it from a live-odds sibling such as get_odds 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 Guidelines4/5

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

The opening 'Use for how one match's market moved' plus the 'with include_in_play' clause gives clear conditions for the main and the in-play variant. It stops short of explicitly naming when-not or an alternative (e.g. current prices vs historical movement), so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All YorkerAPI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources