Skip to main content
Glama
DynamicEndpoints

FantasyPros MCP Server

get_sport_news

Retrieve sports news for NFL, MLB, NBA, or NHL with filtering options for injury reports, game recaps, transactions, rumors, and breaking news to support fantasy sports decisions.

Instructions

Get news for a specific sport

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportYesSport to get news for
limitNoNumber of news items to return (max 25)
categoryNoType of news to show

Implementation Reference

  • The main handler function for 'get_sport_news' tool. It extracts parameters like sport, limit, and category, makes an API call to FantasyPros /${sport}/news endpoint, and returns the JSON response as text content.
    private async getNews(args: any) {
      const { sport, limit = 25, category } = args;
      const params: any = { limit };
      if (category) params.category = category;
    
      const response = await this.axiosInstance.get(`/${sport}/news`, { params });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'get_sport_news' tool, specifying parameters like sport (required, enum), limit, and category.
    inputSchema: {
      type: 'object',
      properties: {
        sport: {
          type: 'string',
          enum: ['nfl', 'mlb', 'nba', 'nhl'],
          description: 'Sport to get news for',
        },
        limit: {
          type: 'number',
          description: 'Number of news items to return (max 25)',
          minimum: 1,
          maximum: 25,
        },
        category: {
          type: 'string',
          enum: ['injury', 'recap', 'transaction', 'rumor', 'breaking'],
          description: 'Type of news to show',
        },
      },
      required: ['sport'],
    },
  • src/index.ts:53-78 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'get_sport_news',
      description: 'Get news for a specific sport',
      inputSchema: {
        type: 'object',
        properties: {
          sport: {
            type: 'string',
            enum: ['nfl', 'mlb', 'nba', 'nhl'],
            description: 'Sport to get news for',
          },
          limit: {
            type: 'number',
            description: 'Number of news items to return (max 25)',
            minimum: 1,
            maximum: 25,
          },
          category: {
            type: 'string',
            enum: ['injury', 'recap', 'transaction', 'rumor', 'breaking'],
            description: 'Type of news to show',
          },
        },
        required: ['sport'],
      },
    },
  • src/index.ts:175-176 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes to the getNews handler function.
    case 'get_sport_news':
      return await this.getNews(request.params.arguments);
Behavior2/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 of behavioral disclosure. It states the tool 'Get news' but does not clarify aspects such as data freshness, rate limits, authentication needs, or potential side effects. For a read operation without annotations, this leaves significant behavioral traits undocumented.

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: 'Get news for a specific sport.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity, making it highly concise and well-structured.

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. It does not explain return values, error handling, or behavioral constraints. For a tool with three parameters and read-only nature implied by 'Get', more context is needed to fully guide an AI agent, such as what the news output looks like or any limitations.

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 description coverage is 100%, with all parameters well-documented in the schema (e.g., 'sport' with enum values, 'limit' with min/max, 'category' with enum). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage nuances, so it meets the baseline for high schema coverage without enhancement.

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 'Get news for a specific sport' clearly states the verb ('Get') and resource ('news for a specific sport'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'get_all_news' (which might fetch news across all sports), leaving room for ambiguity in 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_all_news' or other siblings. It lacks explicit instructions on context, prerequisites, or exclusions, offering only a basic statement of function without comparative or situational advice.

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