Skip to main content
Glama
proplineapi

PropLine

Official

propline_get_player_history

Retrieve a player's prop history across recent games, including lines, prices, and actual values, with redacted details on free tier.

Instructions

Player prop history across recent games. Returns each prior prop this player took with line, prices, resolution, and actual value. Pro tier returns full data; free tier returns redacted resolution/actual_value with an upgrade pointer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sport_keyYes
player_nameYesPlayer name as it appears in box scores — e.g. 'Aaron Judge', 'Nikola Jokic'
limitNoMax number of past games (default 20, max 100)
marketsNoComma-separated subset of markets (e.g. 'player_points,player_rebounds')

Implementation Reference

  • src/index.ts:288-326 (registration)
    Tool 'propline_get_player_history' is defined in the tools array with its name, description, input schema, and an inline handler that delegates to client().getPlayerHistory(). This is where the tool is registered for MCP discovery (ListToolsRequestSchema) and invocation (CallToolRequestSchema).
    {
      name: "propline_get_player_history",
      description:
        "Player prop history across recent games. Returns each prior prop " +
        "this player took with line, prices, resolution, and actual value. " +
        "Pro tier returns full data; free tier returns redacted " +
        "resolution/actual_value with an upgrade pointer.",
      inputSchema: {
        type: "object",
        properties: {
          sport_key: { type: "string" },
          player_name: {
            type: "string",
            description:
              "Player name as it appears in box scores — e.g. 'Aaron Judge', 'Nikola Jokic'",
          },
          limit: {
            type: "number",
            description: "Max number of past games (default 20, max 100)",
          },
          markets: {
            type: "string",
            description:
              "Comma-separated subset of markets (e.g. 'player_points,player_rebounds')",
          },
        },
        required: ["sport_key", "player_name"],
        additionalProperties: false,
      },
      handler: (args) =>
        client().getPlayerHistory(
          args.sport_key as string,
          args.player_name as string,
          {
            limit: args.limit as number | undefined,
            markets: args.markets as string | undefined,
          },
        ),
    },
  • The inputSchema for 'propline_get_player_history' defines four properties: sport_key (string, required), player_name (string, required), limit (number, optional), and markets (string, optional). It also sets additionalProperties: false.
    inputSchema: {
      type: "object",
      properties: {
        sport_key: { type: "string" },
        player_name: {
          type: "string",
          description:
            "Player name as it appears in box scores — e.g. 'Aaron Judge', 'Nikola Jokic'",
        },
        limit: {
          type: "number",
          description: "Max number of past games (default 20, max 100)",
        },
        markets: {
          type: "string",
          description:
            "Comma-separated subset of markets (e.g. 'player_points,player_rebounds')",
        },
      },
      required: ["sport_key", "player_name"],
      additionalProperties: false,
    },
  • The handler for 'propline_get_player_history' is an inline function that calls client().getPlayerHistory() with the sport_key, player_name, limit, and markets arguments.
    handler: (args) =>
      client().getPlayerHistory(
        args.sport_key as string,
        args.player_name as string,
        {
          limit: args.limit as number | undefined,
          markets: args.markets as string | undefined,
        },
      ),
  • The getPlayerHistory method on PropLineClient sends a GET request to /v1/sports/{sportKey}/players/{playerName}/history with optional query params limit and markets. This is the actual API call that powers the tool.
    getPlayerHistory(
      sportKey: string,
      playerName: string,
      opts: { limit?: number; markets?: string } = {},
    ): Promise<unknown> {
      return this.request(
        `/v1/sports/${sportKey}/players/${encodeURIComponent(playerName)}/history`,
        { limit: opts.limit, markets: opts.markets },
      );
    }
Behavior3/5

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

The description discloses tier-based data redaction for free tier and mentions return fields. However, it does not address rate limits, idempotency, or other potential side effects, leaving gaps in behavioral understanding.

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?

Two sentences with no fluff. Front-loaded with key purpose, then adds tier detail. Efficient and well-structured.

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

Completeness3/5

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

With 4 parameters, no output schema, and no annotations, the description explains return fields and tier behavior but lacks detail on parameter interactions and output format. Adequate but not comprehensive.

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 coverage is 75%. The description adds minimal value beyond the schema by summarizing returned data but does not clarify how parameters like 'limit' or 'markets' affect output.

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 clearly states it returns player prop history with specific fields like line, prices, resolution, and actual value. It distinguishes tiers but does not explicitly differentiate from sibling tools, though the name implies uniqueness.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternative propline tools. The only context is a tier difference (pro vs free), but no prerequisites or usage scenarios are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/proplineapi/propline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server