Skip to main content
Glama

FanDuel slates

invoke_fd_slates
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. FanDuel DFS slates for a sport over the next days: slate_id, name, contest type (Full Roster or SingleGame), date, start time ET, games and the main slate flag. FanDuel only; DraftKings slates come from the _list_slates tools.

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

Input Schema

NameRequiredDescriptionDefault
sportYesSport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the first call triggers an approval prompt, plus the visible return fields and that times are ET. It does not mention rate limits, result caps, or pagination.

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?

Two short sentences, no filler, with the platform-exclusion rule stated up front before the field list. The leading note about first-call approval is slightly cryptic ('Added after you connected'), but it is brief and useful, so the cost is small.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description supplies the return payload fields, time-zone convention, contest-type values, and cross-platform routing, which is everything an agent needs to call it correctly. The first-call approval warning closes the last operational gap.

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%, and the single sport parameter is an enum with its own description, so the schema carries the parameter burden and baseline 3 applies. The description adds only that the sport determines which slates and games appear over the next days, which is modest value beyond the enum.

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?

The description states the specific resource (FanDuel DFS slates) scoped by sport and time window, and enumerates the returned fields (slate_id, name, contest type with its Full Roster/SingleGame values, date, start time ET, games, main slate flag). It also names the sibling family (<sport>_list_slates) that serves DraftKings, so an agent can distinguish it from alternatives without opening a 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?

It gives a clear routing rule: use this for FanDuel, use the <sport>_list_slates tools for DraftKings, and it implies the scope is the upcoming days. There is no explicit statement of when not to use it beyond the platform split (e.g., historical slates or other DFS sites), but the primary selection decision is covered.

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