Skip to main content
Glama
Sign In
polygon-mcp

polygon-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

stocks_get_quotes_v3

Retrieve NBBO quotes for a stock with filters for timestamp, sort, and limit. Access real-time and historical quote data to analyze market liquidity.

Instructions

Get NBBO quotes for a stock in a given time range (v3 API).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "stocks_get_quotes_v3"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
orderNo
symbolYes
timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the tool's core purpose. It does not mention output format, pagination behavior, how timestamp/range is interpreted, or any related side effects or limitations.

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, front-loaded sentence with no wasted words. It efficiently communicates the essential resource and action without filler.

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 5 parameters, no annotations, and no output schema, the one-sentence description is insufficient. It omits return value shape, parameter details, and behavioral nuances, making it hard for an agent to invoke correctly without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 5 parameters with 0% description coverage, so the description must compensate. It hints at 'stock' (symbol) and 'time range' (timestamp) but provides no explanation of sort, order, limit, or how timestamp defines the range, leaving most parameter semantics unexplained.

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

Purpose5/5

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

The description clearly states the action ('Get'), the resource ('NBBO quotes'), and the scope ('for a stock in a given time range'), distinguishing it from related tools like stocks_get_quotes and stocks_get_last_quote by naming the v3 API and NBBO quote type.

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?

There is no guidance on when to use this tool versus alternatives such as stocks_get_quotes or stocks_get_last_quote. The mention of 'v3 API' hints at versioning but does not provide explicit selection criteria, exclusions, or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools