Skip to main content
Glama
DynamicEndpoints

FantasyPros MCP Server

get_all_news

Retrieve sports news from FantasyPros for fantasy sports analysis, with filtering by category and adjustable result limits.

Instructions

Get all news from FantasyPros

Input Schema

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

Implementation Reference

  • The handler function that executes the get_all_news tool. It extracts limit and category from args, makes an API call to FantasyPros '/json/all/news' endpoint, and returns the JSON response as text content.
    private async getAllNews(args: any) {
      const { limit = 25, category } = args;
      const params: any = { limit };
      if (category) params.category = category;
    
      const response = await this.axiosInstance.get('/json/all/news', { params });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The input schema defining the parameters for the get_all_news tool: optional limit (1-25) and category (enum of news types).
    inputSchema: {
      type: 'object',
      properties: {
        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 items to show',
        },
      },
    },
  • src/index.ts:149-168 (registration)
    The tool registration entry in the ListTools handler, specifying name, description, and input schema.
    {
      name: 'get_all_news',
      description: 'Get all news from FantasyPros',
      inputSchema: {
        type: 'object',
        properties: {
          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 items to show',
          },
        },
      },
    },
  • src/index.ts:183-184 (registration)
    The switch case in the CallToolRequest handler that dispatches to the getAllNews method.
    case 'get_all_news':
      return await this.getAllNews(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 what the tool does but fails to mention critical details such as whether it's read-only, if it has rate limits, authentication requirements, or what the output format looks like (e.g., list of news items with fields). This leaves significant gaps for an agent to understand the tool's behavior.

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 that directly states the tool's purpose without any unnecessary words or fluff. It is appropriately sized and front-loaded, 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 the complexity of a news retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., news items structure), potential errors, or behavioral traits like pagination or sorting. This leaves the agent with insufficient context for effective use.

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 has 100% description coverage, clearly documenting both parameters (limit and category) with details like max value and enum options. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for adequate but not enhanced semantics.

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 the resource 'all news from FantasyPros', making the purpose understandable. However, it doesn't differentiate from the sibling tool 'get_sport_news', which likely serves a similar purpose with different scope or filtering.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_sport_news' or other siblings. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent with minimal direction.

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