Skip to main content
Glama

Recorded ADP player history

get_adp_history
Read-onlyIdempotent

One player in one required slate. Free: seven days of daily history; Developer: recorded daily history; Production/Scale: hourly. No interpolated dates or implied pre-collection history.

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": {
      "player_id": "<player_id>",
      "slate": "<slate>"
    },
    "name": "get_adp_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoInclusive New York date.
fromNoInclusive New York date.
limitNoRequested rows, default 50, maximum 500; oversized values are rejected.
slateYesTracked public slate ID. ADP is specific to this slate.
cursorNoOpaque cursor bound to filters and snapshot. Hourly current boards cannot be paged.
intervalNoFree: daily seven-day window. Developer: all recorded daily history. Production/Scale: hourly.day
player_idYesStable public player ID from an ADP board.
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds substantive context beyond those annotations: plan-dependent retention/granularity and the caveat that dates are not interpolated and pre-collection history is not implied. Missing return-format, ordering, and pagination detail keeps it from 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 terse sentences or fragments front-load scope, tier availability, and the interpolation caveat with no filler. Every statement carries information relevant to calling the tool.

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?

For an 8-parameter tool with no output schema, the description explains scope and plan-dependent history windows but says nothing about returned row shape, ordering, or pagination beyond what the schema already covers. Core calling constraints are available from schema and annotations, but important output expectations are left unstated.

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 player_id, slate, interval, cursor, from/to, limit, and user_request are already fully documented. The description mostly restates the required player/slate scope and plan-tier interval behavior already present in the schema, adding only the no-interpolation caveat for date parameters; baseline 3 is appropriate.

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 the resource and scope ('One player in one required slate') and, with the name/title, makes clear that it retrieves recorded ADP history for a specific player and slate. It does not explicitly contrast with get_adp or other siblings, so it is clear but not fully differentiated.

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 provides plan-tier availability and required slate context, which helps determine whether the requested granularity is accessible. However, it never says when to use this tool instead of get_adp, get_board_at, or other historical tools, and gives no explicit exclusions; usage is only implied by the name and scope.

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