Skip to main content
Glama
Sign In

Polygon Io

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Grouped Daily

grouped_daily
Read-onlyIdempotent

Fetch OHLCV bars for all US stocks on a given date (YYYY-MM-DD) from Massive (formerly Polygon.io) in a single call; useful for market-wide snapshot or screening.

Input Schema

NameRequiredDescriptionDefault
dateYes
adjustedNo

Output Schema

NameRequiredDescriptionDefault
countNoNumber of results
statusNoAPI response status
resultsNoDaily data for all tickers
field_legendNoLegend for the single-letter OHLC bar keys (o/h/l/c/v/vw/n/t).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2024-01-15"
-  }
-]New value: +[
+  {
+    "date": "2026-09-25"
+  }
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / field_legend
      Added value: +{
+  "description": "Legend for the single-letter OHLC bar keys (o/h/l/c/v/vw/n/t).",
+  "type": "object"
+}
    • addedOutput schema / properties / results / items / properties / date
      Added value: +{
+  "description": "Bar start as an ISO 8601 timestamp (derived from `t`).",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date": "2024-01-15"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of results",
+      "type": "number"
+    },
+    "results": {
+      "description": "Daily data for all tickers",
+      "items": {
+        "properties": {
+          "T": {
+            "description": "Ticker symbol",
+            "type": "string"
+          },
+          "c": {
+            "description": "Close price",
+            "type": "number"
+          },
+          "h": {
+            "description": "High price",
+            "type": "number"
+          },
+          "l": {
+            "description": "Low price",
+            "type": "number"
+          },
+          "n": {
+            "description": "Number of transactions",
+            "type": "number"
+          },
+          "o": {
+            "description": "Open price",
+            "type": "number"
+          },
+          "t": {
+            "description": "Timestamp",
+            "type": "number"
+          },
+          "v": {
+            "description": "Volume",
+            "type": "number"
+          },
+          "vw": {
+            "description": "Volume weighted average",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "API response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds useful context ('single call', upstream source) but says nothing about the size/volume of the result, pagination, or how the 'adjusted' flag alters output. Lower bar applies because annotations carry the behavioral load.

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?

One tight sentence, front-loaded with the verb and resource, with format and data source packed in without waste. Nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation. However, for a market-wide pull of all US stocks, the description omits result volume/pagination expectations and the meaning of 'adjusted', leaving a 2-parameter tool only partially specified.

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?

Schema description coverage is 0%, so the description must compensate. It supplies the expected date format (YYYY-MM-DD), but the second parameter, 'adjusted', is left completely unexplained in both schema and description -- a meaningful gap for a price-data tool where adjustment semantics matter.

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?

Specific verb (Fetch) plus resource (OHLCV bars for all US stocks), scoped to a single date, and names the data source. The 'all US stocks' scope plus 'single call' clearly differentiates it from sibling tools like aggregates, daily_open_close, or previous_close, which operate on narrower scopes.

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?

Gives clear context -- 'useful for market-wide snapshot or screening' -- which tells the agent when this tool fits. It stops short of naming alternatives or exclusions (e.g., 'use aggregates for a single ticker'), so guidance is present but not routing-grade.

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

All Polygon Io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources