Skip to main content
Glama
Sign In

FanDuel API

by com.fanduelapi
OverviewDiscussionsAdmin

answer_onboarding

Answer the onboarding questions for your user, from what you know about their project. Ask them what you do not know; never guess. Answering again replaces the answers; the same answers twice change nothing. Your user sees them on their dashboard, marked as answered by their agent. Costs no quota.

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": {
      "answers": "<answers>"
    },
    "name": "answer_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNoYour name, such as Claude Code or Cursor.
answersYesQuestion id to answer. A select question takes one of its options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses idempotent/replacement semantics ('answering again replaces the answers; the same answers twice change nothing'), the user-visible side effect (shown on the dashboard, attributed to the agent), and cost ('costs no quota').

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?

Five short sentences, front-loaded with purpose, then sourcing rule, idempotency, visibility, and cost — no filler and every sentence carries distinct information.

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 nested-object mutation with no annotations and no output schema, the description covers side effects, idempotency, and cost, which is most of what an agent needs. The remaining gap is how to obtain the valid question ids (the get_onboarding_questions sibling is never mentioned).

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 100% and each field is described in the schema, including the use_case enum and nested answers object, so the description adds little parameter-level detail. It confirms the answers are project-derived and must not be fabricated, which is mild added 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 and resource ('Answer the onboarding questions for your user') plus the data source ('from what you know about their project'). It does not name the obvious companion tool get_onboarding_questions for discovering the question ids, so sibling differentiation is implicit rather than explicit.

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 clear operating guidance: answer from known project context, ask the user for anything unknown, and never guess. It lacks an explicit 'call get_onboarding_questions first' routing statement and says nothing about when not to answer at all.

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

All FanDuel API toolsInspect
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