Skip to main content
Glama

DFS Lineup Optimizer

List sample slates

list_lineup_examples
Read-only

List the bundled sample slates, one per sport (real past DraftKings Classic slates). Each can be built as-is with build_lineups(example=...).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_lineup_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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=false, so the safety profile is covered by structured data. The description contributes useful context beyond that — the entries are real historical DraftKings Classic slates, one per sport, and are directly consumable as build_lineups examples. It does not state how many slates come back or the shape of each entry.

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 short sentences, zero filler, with the resource description front-loaded and the follow-up action placed second. Every clause carries information an agent needs.

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 zero-parameter, read-only listing tool with no output schema, the description covers what is returned (bundled samples, one per sport), what they are (real past DraftKings Classic slates), and how to use them (build_lineups(example=...)). Only the per-item field structure is left unstated, which is a minor gap given the simplicity.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline for a no-param tool applies. The description does not describe the returned objects or their distinguishing fields (sport, slate name), which would be the only useful 'parameter-like' detail here.

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?

Uses a specific verb+resource ("List the bundled sample slates") and scopes it ("one per sport, real past DraftKings Classic slates"), which clearly distinguishes it from build_lineups. It does not explicitly contrast with the singular sibling get_lineup_example, so sibling differentiation is implied by the plural phrasing rather than stated.

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 clear downstream use: the returned slates can be passed straight into build_lineups(example=...), which tells the agent when this tool is the right entry point. There is no explicit when-not guidance or statement about the alternative get_lineup_example path, but the context is unambiguous.

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