Skip to main content
Glama

DFS Lineup Optimizer

Get an example lineup request

get_lineup_example
Read-only

Return a ready-to-run build_lineups request for a sport using its bundled sample slate, a short preview of the slate, the player-list format, and the rules available for that sport.

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": "get_lineup_example"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: the slate is a 'bundled sample' (fixture data, not live) and the response is decomposed into four named parts, which matters since there is no output 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?

One sentence, front-loaded with the primary outcome ('ready-to-run build_lineups request') before the supporting detail. The trailing list of returned artifacts is dense but each item earns its place since there is no output schema.

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 one-parameter, non-destructive lookup with no output schema, the description covers what is returned and that the data is a bundled sample. Minor gaps remain: no indication of response size, whether the request is directly passable to build_lineups without editing, or how it differs from list_lineup_examples.

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 single parameter is named 'sport' in the description and its enum of four leagues is fully self-documenting in the schema, so little is missing. The description adds only that each sport has its own bundled sample slate, which is a marginal elaboration rather than new meaning.

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?

States a specific verb ('return') and a concrete resource ('a ready-to-run build_lineups request'), plus enumerates what comes back (sample slate preview, player-list format, available rules). This clearly marks it as an example-generator rather than the executor, though it never names build_lineups or list_lineup_examples to make the distinction explicit.

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?

Usage is only implied: an agent can infer this is for obtaining a template before calling build_lineups, but the description gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. There is no statement about whether this should be called instead of list_lineup_examples.

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