Skip to main content
Glama
Sign In
polygon-mcp

polygon-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

stocks_get_quotes

Get stock quotes for a specific date by providing a symbol and date. Retrieve historical trading data with an optional limit to analyze market activity.

Instructions

Get quotes for a stock on a specific date (YYYY-MM-DD).

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>",
      "date": "<date>"
    },
    "name": "stocks_get_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
limitNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only says 'Get quotes', adding no context about limit behavior, return format, pagination, or other behavioral characteristics. It is purely a read verb without disclosure of how the tool operates in practice.

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?

A single, compact sentence with no wasted words; it front-loads the action and resource, 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 output schema and 3 parameters, the description is too sparse. It doesn't describe the shape of returned quotes, the effect of the limit, or how this differs from stocks_get_quotes_v3, leaving significant gaps for an agent to infer.

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 supplies the date format (YYYY-MM-DD), which the schema does not, but it fails to explain the 'limit' parameter or clarify that the tool may return multiple quotes. With 0% schema description coverage, more compensation is expected.

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?

Description clearly states the action ('Get quotes'), resource ('a stock'), and scope ('on a specific date'), distinguishing it from siblings like last-quote or forex tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'on a specific date (YYYY-MM-DD)' provides clear context for when to use this tool (historical daily quotes) and implicitly differentiates from real-time or last-quote tools, though it doesn't name explicit alternatives.

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