Skip to main content
Glama

FanDuel projections

invoke_fd_projections
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. BankrollSZN FanDuel projections for one slate: salary, FanDuel points, floor, ceiling, value per $1K, projected ownership and FanDuel player id. NBA and PGA come from the BankrollSZN FanDuel engines; NFL from the FanDuel NFL pool. Default: the first Full Roster slate. Use only when the user asks for FanDuel.

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_projections"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation.
limitNoMaximum rows. The plan limit applies on top.
sportYesnba, pga or nfl.
sort_byNo
positionNoPosition filter, for example PG, C, QB, WR.
slate_idNoslate_id from fd_slates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavior: the first call triggers an approval prompt, a plan limit is layered on top of the requested row count, and data provenance differs by sport (BankrollSZN engines for NBA/PGA, FanDuel NFL pool for NFL). It does not discuss response ordering or what happens when the slate has no rows.

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?

Three dense sentences with no filler, and the approval caveat is front-loaded before the substantive content. The middle field enumeration is long but earns its place because there is no output schema to document return values.

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?

With no output schema, the description carries the burden of describing returns and does so field by field, and it explains the sport-to-source mapping that an agent would otherwise have to guess. Minor gaps remain around pagination/row caps and what an empty slate response looks like.

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 coverage is 83%, so the schema already explains sport, team, position, limit, sort_by and slate_id. The description contributes only the default-slate behavior for slate_id and the source-by-sport distinction; it adds nothing about the sort_by enum values or the interaction between limit and the plan cap. Baseline 3 is appropriate.

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 resource (FanDuel projections for one slate) and enumerates exactly what each row contains: salary, FanDuel points, floor, ceiling, value per $1K, ownership and player id. The closing 'Use only when the user asks for FanDuel' separates it from the per-sport siblings like invoke_nba_projections or invoke_nfl_projections.

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 an explicit exclusion ('only when the user asks for FanDuel') and documents the default behavior (first Full Roster slate) when slate_id is omitted. It stops short of routing the agent to invoke_fd_slates to obtain a slate_id or to the optimizer as a follow-up, so the guidance is clear but not fully connected to alternatives.

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