Skip to main content
Glama

Recorded ADP by slate

get_adp
Read-onlyIdempotent

ADP is per slate, not a projection or recommendation. Pass sport or slate; list_slates=true lists tracked slates instead. Negative change means rising. Compact daily rows default to 50; full view adds 3-day changes when recorded. Preserve snapshot_date, history_starts, slate_status and adp_note. No pick ranges, draft counts or ownership are supplied.

Input Schema

NameRequiredDescriptionDefault
dateNoRecorded New York daily snapshot date; not valid with fresh=hour.
kindNoFilter the measured slate kind.all
sortNoDaily change sorts retain missing values as null.adp
teamNoTeam abbreviation
viewNoCompact defaults to one credit/100 requested rows, maximum 1000. Full costs two/100, maximum 500.compact
freshNoDaily for Free; hourly current requires Developer. Hourly current does not support cursors or change sorting.day
limitNoRequested rows, default 50, maximum 1000; oversized values are rejected.
slateNoTracked public slate ID. ADP is specific to this slate.
sportNoSport code; sport or slate is required for a board or movers. No coverage implied.
cursorNoOpaque cursor bound to filters and snapshot. Hourly current boards cannot be paged.
searchNoPlayer name substring, at most 100 characters
statusNoOnly with list_slates=true.
draftedNoTrue excludes undrafted players; false includes both.
positionNoPosition filter
list_slatesNoReturn tracked slate catalog instead; only sport, kind and status filters apply.
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

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: negative change values mean a player is rising, compact vs full views differ in cost and in whether 3-day changes appear, and specific metadata fields must be preserved. It also discloses scope limits ('no pick ranges, draft counts or ownership'), which prevents false expectations. Pagination/cursor behavior is left to the schema.

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?

Front-loaded with the most important disambiguation (per-slate, not a projection), then mode selection, then semantics and scope. Sentences are terse and each carries information. The telegraphic style ('Compact daily rows default to 50') is slightly clipped but not wasteful.

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 16-parameter tool with no output schema, the description covers what matters most: how to pick a mode, what the rows represent, how to read change values, and what data is deliberately absent. Cost/credit and cursor mechanics are delegated to the schema, which is acceptable given 100% schema coverage. An explicit statement that results are recorded snapshots rather than live data would close the remaining gap.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: the inversion that negative change means rising (critical for interpreting sort=change_1d/change_7d output), the exclusivity of list_slates, and the sport-or-slate requirement. It does not explain the user_request or fresh/cursor interactions beyond what the schema already says.

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 names the resource precisely (recorded ADP, per slate) and explicitly rules out two plausible misreadings: it is 'not a projection or recommendation'. It also states the alternate mode (list_slates=true returns the slate catalog). It stops short of an explicit verb phrase like 'returns recorded ADP rows', so it is clear but slightly implicit.

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?

'Pass sport or slate; list_slates=true lists tracked slates instead' gives the agent a concrete routing rule between the two modes, matching the anyOf constraint in the schema. It does not contrast with the closest sibling (get_adp_history) or say when to prefer this over get_board_at, so guidance is clear but incomplete.

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