Skip to main content
Glama
DynamicEndpoints

FantasyPros MCP Server

get_players

Retrieve detailed player information for NFL, MLB, NBA, or NHL sports to support fantasy sports research and decision-making.

Instructions

Get player information for a specific sport

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportYesSport to get players for
playerIdNoFilter by specific player ID

Implementation Reference

  • The handler function that executes the get_players tool: fetches player data from FantasyPros API for the specified sport and optional playerId, returns JSON response.
    private async getPlayers(args: any) {
      const { sport, playerId } = args;
      const params: any = {};
      if (playerId) params.player = playerId;
    
      const response = await this.axiosInstance.get(`/${sport}/players`, { params });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Input schema for the get_players tool, defining sport (required, enum) and optional playerId.
    inputSchema: {
      type: 'object',
      properties: {
        sport: {
          type: 'string',
          enum: ['nfl', 'mlb', 'nba', 'nhl'],
          description: 'Sport to get players for',
        },
        playerId: {
          type: 'string',
          description: 'Filter by specific player ID',
        },
      },
      required: ['sport'],
    },
  • src/index.ts:79-97 (registration)
    Registration of the get_players tool in the tools list returned by ListToolsRequestHandler.
    {
      name: 'get_players',
      description: 'Get player information for a specific sport',
      inputSchema: {
        type: 'object',
        properties: {
          sport: {
            type: 'string',
            enum: ['nfl', 'mlb', 'nba', 'nhl'],
            description: 'Sport to get players for',
          },
          playerId: {
            type: 'string',
            description: 'Filter by specific player ID',
          },
        },
        required: ['sport'],
      },
    },
  • src/index.ts:177-178 (registration)
    Dispatch/registration in the CallToolRequestHandler switch statement, routing to the getPlayers handler.
    case 'get_players':
      return await this.getPlayers(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' information, implying a read operation, but doesn't cover aspects like permissions, rate limits, response format, or whether it's safe/destructive. This leaves significant gaps for a tool with parameters.

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, efficient sentence with zero waste, clearly front-loading the purpose. It's appropriately sized for a simple tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a tool with parameters. It lacks behavioral context, usage guidance, and details on return values, making it inadequate for full agent understanding despite the clear schema.

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 description coverage is 100%, so the schema already documents both parameters fully. The description adds no additional meaning beyond implying 'sport' is required and 'playerId' is optional for filtering, which is already clear from the schema. Baseline 3 is appropriate as 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?

The description clearly states the verb 'Get' and resource 'player information' with scope 'for a specific sport', making the purpose understandable. However, it doesn't differentiate from potential sibling tools like 'get_rankings' or 'get_projections' that might also involve player data, missing full sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_rankings' or 'get_projections', nor does it mention prerequisites or exclusions. It only implies usage by stating the purpose without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DynamicEndpoints/fantasy-pros-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server