StrikerAPI

Prop movement

get_prop_movement

Read-onlyIdempotent

Use to see how one player's prop line moved before a game: every capture we hold, book by book and oldest first, with the line, both prices and the minutes before the start. line_change is the last capture's line minus the first's. The number of captures varies by game and book. 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": {
      "game_id": "<game_id>",
      "player_id": "<player_id>",
      "market": "<market>"
    },
    "name": "get_prop_movement"
  }
}

Input Schema

Name	Required	Description
`league`	No	League. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl.
`market`	Yes	The market: player_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists), player_first_goal_scorer (first goalscorer (over = scores the match's first goal)), player_last_goal_scorer (last goalscorer (over = scores the match's last goal)), player_to_receive_card (to be carded (over = shown a yellow or red card))
`game_id`	Yes	Game id.
`bookmaker`	No	One book's captures, e.g. draftkings.
`player_id`	Yes	Player id (e.g. 280555) from search_players.

Output Schema

Name	Required	Description	Default
`note`	No
`tool`	No
`books`	Yes
`count`	Yes
`market`	Yes
`credits`	No
`game_id`	Yes
`player_id`	Yes
`player_name`	Yes
`estimate_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the return shape (every capture, ordered oldest first, with line, both prices and minutes before start), that capture count varies by game and book, what line_change means arithmetically, and the credit cost. It also adds a hard usage constraint about never computing stakes/payouts or recommending a bet, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is front-loaded with the core purpose and then layers ordering, line_change semantics, variability and cost. Every sentence carries information, though the closing compliance sentence is dense and could be split for readability.

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

Completeness4/5

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

For a read-only lookup with an output schema already present, the description covers cost, data variability, ordering and the derived line_change field. The only minor gap is that no sibling alternative is named for agents deciding between the several prop and line-movement tools.

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 100%, so the baseline is 3. The description reinforces the bookmaker filter ('book by book') and clarifies that line_change compares the last and first capture, but it adds no guidance on the enums, defaults, or the interaction between game_id and player_id.

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 states a specific verb and resource: it shows how one player's prop line moved across every capture held, book by book, oldest first. The scoping to props for a single player implicitly separates it from the sibling get_line_movement (game lines) and get_prop_history, though it never names those alternatives outright.

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?

It opens with 'Use to see...' and gives a useful decision input by stating the 10-credit cost, but it offers no explicit when-not guidance and does not mention get_prop_history, get_player_props, or get_line_movement as alternatives for adjacent needs.

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

All StrikerAPI tools Inspect

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.