Skip to main content
Glama
jwaresolutions

Polygon MCP Server

get_snapshot

Retrieve current market data snapshots for specified stock tickers to analyze real-time financial performance and trading metrics.

Instructions

Get snapshot of ticker(s)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickersYesComma-separated list of tickers (e.g., AAPL,MSFT,GOOGL)

Implementation Reference

  • The async handler function implementing the 'get_snapshot' tool logic. It calls the Polygon API to retrieve snapshot data for given tickers and formats the response as text content or handles errors.
    get_snapshot: async (args: { tickers: string }) => {
      try {
        const response = await polygonApi.get('/v2/snapshot/locale/us/markets/stocks/tickers', {
          params: {
            tickers: args.tickers
          }
        });
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `Error getting snapshot: ${error.response?.data?.message || error.message}`
          }],
          isError: true
        };
      }
    }
  • The input schema definition for the 'get_snapshot' tool, specifying the required 'tickers' parameter as a string.
    inputSchema: {
      type: "object",
      properties: {
        tickers: {
          type: "string",
          description: "Comma-separated list of tickers (e.g., AAPL,MSFT,GOOGL)"
        }
      },
      required: ["tickers"]
    }
  • src/index.ts:384-396 (registration)
    The tool registration entry in the ListTools response, including name, description, and input schema for 'get_snapshot'.
      name: "get_snapshot",
      description: "Get snapshot of ticker(s)",
      inputSchema: {
        type: "object",
        properties: {
          tickers: {
            type: "string",
            description: "Comma-separated list of tickers (e.g., AAPL,MSFT,GOOGL)"
          }
        },
        required: ["tickers"]
      }
    }
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 'Get snapshot' but doesn't clarify if this is a read-only operation, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps for a tool that likely fetches financial data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. However, it's overly terse and could benefit from slightly more detail to improve clarity without sacrificing brevity.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'snapshot' returns (e.g., current prices, volumes, etc.), leaving the agent uncertain about the tool's behavior and output, which is inadequate for a data-fetching tool in a financial context.

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%, with the 'tickers' parameter fully documented as a comma-separated list. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, so it meets the baseline score of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get snapshot of ticker(s)' states the basic action (get) and target (snapshot of tickers), but it's vague about what a 'snapshot' entails compared to siblings like 'get_ticker_details' or 'get_latest_quote'. It doesn't specify what data the snapshot includes, making it less distinct from alternatives.

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 siblings such as 'get_ticker_details' or 'get_latest_quote'. The description implies it retrieves data for tickers, but without context on what makes a 'snapshot' different, the agent lacks clear usage criteria.

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