Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

start_signup

Initiates signup by collecting your email and use case, then sends an approval link to authorize access. Call after gathering details to begin onboarding before finishing setup.

Instructions

Start a key for your user. Ask them for their email and what they are building; never guess. They approve an emailed link (signing in first if the email already has an account); then call finish_signup.

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": {
      "email": "<email>",
      "use_case": "<use_case>"
    },
    "name": "start_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOptional. The ref value from the link you found this API through, such as ai-claudebot.
agentNoYour name, plain words, up to 60 characters.
emailYesYour user's own email address.
sportsNoWhich sports matter most.
use_caseYesWhat they are building.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 substantial work: it discloses that the user must approve an emailed link, that existing accounts sign in first, and that a second call (finish_signup) is required. It does not describe what this call returns or how failures surface, which keeps it below a 5.

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?

Purpose is front-loaded, followed by the collection instruction and the approval/follow-up flow in a compact block. The parenthetical slightly interrupts the flow but nothing is wasted or redundant.

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 two-step signup tool with no output schema and no annotations, the description covers prerequisites, required user input, and the next step. The notable gap is that it never says what the agent receives back from this call, but the workflow itself is adequately explained.

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%, so all five parameters are already documented in the schema. The description only reinforces which two to ask the user for (email, use-case) and adds no meaning for ref, agent, or sports. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"Start a key for your user" gives a specific verb (start) and resource (a key/signup), and the closing "then call finish_signup" distinguishes it from the sibling that completes the flow. It stops short of saying explicitly that this issues an API key and triggers an email, but an agent can tell the two signup steps apart.

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 tells the agent to collect email and use-case and to "never guess," and it names the follow-up (finish_signup) plus the in-flow branch where an existing account must sign in first. It doesn't state when not to call this (e.g. already has a key), so there's no explicit exclusion, but the when-to-use context is clear.

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