Skip to main content
Glama

DFS Lineup Optimizer

Check a lineup request

check_request
Read-only

Validate a build_lineups request WITHOUT solving: arguments, rule names and ranges, that the players parse, that locks/exclusions/projection names match real players, and that every roster slot has enough eligible players. Takes the same arguments as build_lineups. Fast.

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": {
      "sport": "<sport>"
    },
    "name": "check_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoContest site (default dk). 'players' as a list works for dk only; fd and yahoo need the site's raw CSV text.
rulesNoSport-specific rules, using the web app's option names. Each is tagged with the sports it applies to; a rule for another sport is an error. get_lineup_example(sport) lists the ones for that sport.
sportYes
exampleNoUse a bundled sample slate instead of players (names from list_lineup_examples, or just the sport). Live lookups are skipped.
playersNoEITHER the raw salary CSV text exactly as exported from the contest site (DraftKings 'Download players' / FanDuel players list / Yahoo export; a Classic contest), OR a list of player objects (site dk only).
n_lineupsNoLineups to build (default 10, max 20: diversity cuts make each extra lineup slower and the free server is small).
min_salaryNoLineups must spend at least this much.
projectionsNoYour own projections as {player name or id: points}; overrides the file's AvgPointsPerGame for those players. Names are matched case-insensitively.
live_lookupsNoNHL line combos / starting goalies and MLB batting orders / probable pitchers from the public sites the web page uses (default false: skipped; sample slates always skip). Can fail or be slow; a failure is reported, the solve still runs.
lock_playersNoPlayers (name or id) that must be in every lineup.
exclude_playersNoPlayers (name or id) to leave out.
max_exposure_pctNoAny one player may appear in at most this % of the lineups (100 = no cap).
exclude_out_playersNoDrop players the file marks OUT/IL (default true, as the web page does).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that, adding that no solve is performed and that it is fast. It also implicitly discloses live-lookup behavior by listing 'projection names match real players' as a check, though it does not say whether live lookups are made during validation or what the output shape of the validation report is.

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?

One front-loaded sentence naming the verb, the negated scope, and the enumerated checks, followed by a short parity note and a one-word performance claim. Every clause carries information.

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 13-parameter validation tool with rich schema coverage and no output schema, the description sets expectations adequately. The main gap is the return value: with no output schema, an agent is not told what a check report looks like (pass/fail flags, error list), though 'without solving' and 'Fast' convey the salient behavior.

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 92%, so the nested rules and player objects are already well documented and the description correctly claims argument parity with build_lineups rather than restating them. The description adds only the indirect hint that locks, exclusions, and projection names are resolved against a real player pool, which affects how those name arguments must be formatted; nothing else goes beyond the schema.

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?

States a specific verb and resource — 'Validate a build_lineups request WITHOUT solving' — and enumerates exactly what is validated (arguments, rule names and ranges, player parsing, lock/exclusion/projection name matching, roster-slot eligibility). It explicitly positions itself against the sibling build_lineups by saying it does not solve, so an agent can distinguish them without opening either schema.

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?

Implies clear usage: call this before build_lineups to catch bad input cheaply ('Fast'), and it names the sibling whose arguments it mirrors. It stops short of explicit when-not guidance — e.g. it does not say whether a successful check is required before building, or what to do with the reported errors.

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