Skip to main content
Glama
jwaresolutions

Polygon MCP Server

get_ticker_news

Retrieve news articles for a specific stock ticker symbol to monitor market developments and inform investment decisions.

Instructions

Get news articles for a ticker

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker symbol (e.g., AAPL)
limitNoNumber of articles to return (default: 10)

Implementation Reference

  • The handler function for get_ticker_news tool. Fetches news articles for a given ticker symbol using the Polygon API v2/reference/news endpoint. Returns formatted JSON response or error message.
    get_ticker_news: async (args: { ticker: string; limit?: number }) => {
      try {
        const params: any = {
          limit: args.limit || 10
        };
        const response = await polygonApi.get(`/v2/reference/news`, {
          params: {
            ...params,
            ticker: args.ticker
          }
        });
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `Error getting ticker news: ${error.response?.data?.message || error.message}`
          }],
          isError: true
        };
      }
    },
  • src/index.ts:338-355 (registration)
    Tool registration in the ListTools response, defining the name, description, and input schema for get_ticker_news.
    {
      name: "get_ticker_news",
      description: "Get news articles for a ticker",
      inputSchema: {
        type: "object",
        properties: {
          ticker: {
            type: "string",
            description: "Ticker symbol (e.g., AAPL)"
          },
          limit: {
            type: "number",
            description: "Number of articles to return (default: 10)"
          }
        },
        required: ["ticker"]
      }
    },
  • Input schema definition for the get_ticker_news tool, specifying parameters ticker (required string) and optional limit (number).
    inputSchema: {
      type: "object",
      properties: {
        ticker: {
          type: "string",
          description: "Ticker symbol (e.g., AAPL)"
        },
        limit: {
          type: "number",
          description: "Number of articles to return (default: 10)"
        }
      },
      required: ["ticker"]
    }
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 but offers minimal information. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, or what format/news sources are returned. For a tool with no annotations, this is insufficient behavioral context.

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 extremely concise with a single, clear sentence that gets straight to the point. There's no wasted language or unnecessary elaboration, making it efficiently front-loaded and easy to parse.

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 that likely returns complex news data. It doesn't explain the return format, article structure, or any behavioral traits, leaving significant gaps in understanding how to use this tool effectively.

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 description doesn't add any parameter semantics beyond what the input schema already provides (100% coverage). The schema fully documents both parameters (ticker and limit with default), so the baseline score of 3 is appropriate as the description doesn't compensate or add extra meaning.

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 articles for a ticker' clearly states the action (get) and resource (news articles for a ticker), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools that might also retrieve news-related data, keeping it from a perfect score.

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_ticker_details' or other sibling tools. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone.

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/jwaresolutions/polygon-mcp-server'

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