Skip to main content
Glama
jwaresolutions

Polygon MCP Server

get_ticker_details

Retrieve comprehensive information about a specific stock or asset by providing its ticker symbol. This tool accesses financial market data to deliver key details for investment analysis and decision-making.

Instructions

Get details about a ticker symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker symbol (e.g., AAPL)

Implementation Reference

  • The handler function for get_ticker_details that queries the Polygon API for ticker details and returns the response as formatted JSON or an error.
    get_ticker_details: async (args: { ticker: string }) => {
      try {
        const response = await polygonApi.get(`/v3/reference/tickers/${args.ticker}`);
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `Error getting ticker details: ${error.response?.data?.message || error.message}`
          }],
          isError: true
        };
      }
    },
  • src/index.ts:244-257 (registration)
    Tool registration in the ListToolsRequestHandler, providing the tool name, description, and input schema definition.
    {
      name: "get_ticker_details",
      description: "Get details about a ticker symbol",
      inputSchema: {
        type: "object",
        properties: {
          ticker: {
            type: "string",
            description: "Ticker symbol (e.g., AAPL)"
          }
        },
        required: ["ticker"]
      }
    },
  • Input schema definition for the get_ticker_details tool, specifying the required 'ticker' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        ticker: {
          type: "string",
          description: "Ticker symbol (e.g., AAPL)"
        }
      },
      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. It states it 'gets details' but doesn't specify what details are returned, whether it's a read-only operation, error handling, or any rate limits. This is inadequate for a tool with no annotation coverage.

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 no wasted words. It's front-loaded with the core purpose, 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. It doesn't explain what 'details' are returned, error cases, or how it differs from sibling tools. For a tool in a set with multiple similar functions, this leaves significant gaps for an agent.

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%, so the schema already documents the 'ticker' parameter. The description doesn't add any meaning beyond what's in the schema (e.g., examples, constraints, or context), so it meets the baseline for high schema coverage.

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 action ('Get details') and resource ('about a ticker symbol'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_snapshot' or 'get_latest_quote' which might also provide ticker details, leaving room for ambiguity about what specific details are returned.

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_snapshot' or 'get_latest_quote'. The description lacks context about what distinguishes it from siblings, leaving the agent to infer usage based on tool names 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