FanDuel API

get_sample_props

Up to 10 real FanDuel player props, delayed like the free plan, so you can check fit before signup. No key.

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

Input Schema

Name	Required	Description
`stat`	No	points, rebounds, assists, threes and so on.
`limit`	No	1 to 10.
`sport`	No	nba, nfl, nhl, mlb, ncaab or ncaaf.
`player`	No	Part of a player name.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden here, and it does disclose the important traits: the result set is capped at 10, the data is delayed like the free plan, and no API key is required. It omits rate limits, the exact delay, and error behavior, which are secondary for a preview endpoint.

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 with every phrase doing work: resource, cap, data freshness, purpose, and auth status all conveyed up front. There is no filler or repetition.

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?

All four parameters are optional and fully documented by the schema; no output schema exists, but the description states in essence what comes back (up to 10 real but delayed props). Combined with the no-key note, this is nearly everything an agent needs to call it correctly.

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 schema covers 100% of the parameters with its own descriptions for stat, limit, sport, and player. The only added meaning is the 'up to 10' cap, which reinforces the limit parameter's range; nothing else in the text extends 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 a specific resource: real FanDuel player props, capped at 10. The 'sample/no key' framing implicitly distinguishes it from the full authenticated listing sibling, but no sibling is named explicitly, so the differentiation is left to inference.

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?

'so you can check fit before signup. No key.' gives a clear use context, that this is a pre-auth preview tool, which implies the alternative requires a key. It stops short of naming a sibling or stating an explicit when-not condition, such as how to actually get the full prop list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FanDuel API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?