Skip to main content
Glama

get_prop_history

Read-only

Read the recorded line and price changes for one player-prop quote, oldest first, with its open and its close (the last quote before the start). Books with history: fanduel, draftkings, prizepicks, novig, underdog, pick6. Pass the book and the quote id from get_player_props.

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": {
      "book": "<book>",
      "id": "<id>"
    },
    "name": "get_prop_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bookYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / book / enum
      Previous value: -[
      -  "fanduel",
      -  "prizepicks",
      -  "novig",
      -  "underdog"
      -]New value: +[
      +  "fanduel",
      +  "draftkings",
      +  "prizepicks",
      +  "novig",
      +  "underdog",
      +  "pick6"
      +]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that — result ordering and the open/close semantics — but says nothing about the limit truncation behavior or what is returned when a book has no recorded history.

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 short sentences, front-loaded with the core read operation, then the output shape, then the call recipe. No filler or repetition.

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?

No output schema exists, and the description compensates by describing the payload semantics (oldest-first series with open and close). Complete enough to call correctly, with the main gap being limit/pagination behavior and edge cases for books lacking history.

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 must carry parameter meaning. It explains that id is a quote id obtained from get_player_props (real value beyond the regex pattern) and restates the supported book values already enforced by the enum, but the limit parameter (default 200, max 200) is never explained, leaving truncation semantics undefined.

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?

Specific verb plus resource: reads recorded line and price changes for one player-prop quote. It scopes the result explicitly (oldest first, includes open and close, close defined as the last quote before the start), which distinguishes it from the broader get_history and from get_player_props.

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 a concrete prerequisite chain: pass the book and the quote id from get_player_props, and enumerates which books carry history so the agent can avoid unusable calls. It stops short of naming an alternative tool (e.g., get_history) or stating when not to use this one.

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.