DraftCall-MCP

Get one NFL player

get_player

Retrieve a player's fantasy profile: positional rank, points per game in PPR, half-PPR, and standard, season stats, games played, and bye week. Get key data for draft decisions.

Instructions

A single player's fantasy profile: positional rank, points per game in all three scoring formats, season stats, games played, and bye week.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Player name, e.g. "Puka Nacua".

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 25, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes the output (fantasy profile) thoroughly, implying a read-only operation. However, it does not disclose potential limitations such as seasonal scope, data freshness, or error behavior. Still, for a simple getter, the description is reasonably transparent about what it returns.

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?

The description is a single sentence with no filler. The core purpose ('A single player's fantasy profile') is front-loaded, followed by a concise list of contents. Every word earns its place, making it easy to scan.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides enough detail about the return payload. It lists the key data points an agent would expect. It omits possible error handling or caveats but these are less critical for a straightforward getter. Overall, it is fairly complete for its complexity.

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 input schema provides 100% coverage for the only parameter (name) with an example. The description does not add any additional semantic value beyond what the schema already states. Per the rubric, this yields a baseline score of 3, which 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?

The description clearly states the tool returns a single player's fantasy profile, enumerating specific data points like positional rank, points per game in three formats, season stats, games played, and bye week. This is a specific verb-resource pairing that differentiates it from siblings like search_players (searching) and compare_players (comparing). An agent can immediately understand what this tool delivers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a single player's profile is needed, but it does not explicitly state when to use this tool versus alternatives like compare_players or get_rankings. No mention of exclusions or conditions, leaving the agent to infer from context. This is adequate but lacks the explicit guidance seen in better definitions.

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

Deploy Server