IPOGrid IPO Calendar & Filing Research

Get Chart

get_chart

Read-onlyIdempotent

Build an aggregated IPO chart and return its data plus canonical embed, page, and API URLs. Use this instead of hand-building chart URLs. Anonymous requests are quota-limited and may clamp a 52-week range to 26 weeks or a daily bucket to weekly unless the explicit date window is at most 31 days.

Input Schema

TableJSON Schema

Name	Required	Description
`group`	No	Dimension used to split chart series. Defaults to sector for proceeds/returns and form_family for filing counts.
`range`	No	Trailing window when explicit dates are omitted. Defaults to 26w; anonymous 52w requests are clamped to 26w.
`scope`	No	Include all matching records or only active offerings. Defaults to active.
`bucket`	No	Time interval. Defaults to week; anonymous daily requests require an explicit window of at most 31 days or are clamped to week.
`issuer`	No	Include every issuer or exclude SPACs. Defaults to all.
`metric`	No	Value to aggregate. Defaults to gross_proceeds.
`date_to`	No	Inclusive YYYY-MM-DD upper bound. Use with date_from for a custom window instead of range.
`date_from`	No	Inclusive YYYY-MM-DD lower bound. Use with date_to for a custom window instead of range.
`materiality`	No	Include all filing forms or only major IPO forms. Defaults to all.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`links`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedJul 16, 2026

addedInput schema / properties / bucket / description

Added value: +"Time interval. Defaults to week; anonymous daily requests require an explicit window of at most 31 days or are clamped to week."

addedInput schema / properties / date_from / description

Added value: +"Inclusive YYYY-MM-DD lower bound. Use with date_to for a custom window instead of range."

addedInput schema / properties / date_to / description

Added value: +"Inclusive YYYY-MM-DD upper bound. Use with date_from for a custom window instead of range."

addedInput schema / properties / group / description

Added value: +"Dimension used to split chart series. Defaults to sector for proceeds/returns and form_family for filing counts."

addedInput schema / properties / issuer / description

Added value: +"Include every issuer or exclude SPACs. Defaults to all."

addedInput schema / properties / materiality / description

Added value: +"Include all filing forms or only major IPO forms. Defaults to all."

addedInput schema / properties / metric / description

Added value: +"Value to aggregate. Defaults to gross_proceeds."

addedInput schema / properties / range / description

Added value: +"Trailing window when explicit dates are omitted. Defaults to 26w; anonymous 52w requests are clamped to 26w."

addedInput schema / properties / scope / description

Added value: +"Include all matching records or only active offerings. Defaults to active."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "points": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "period": {
+                "description": "Date bucket label.",
+                "type": "string"
+              },
+              "series": {
+                "description": "Grouped series label.",
+                "type": "string"
+              },
+              "value": {
+                "description": "Aggregated value for this bucket and series.",
+                "type": "number"
+              }
+            },
+            "required": [
+              "period",
+              "series",
+              "value"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "spec": {
+          "additionalProperties": {},
+          "description": "Normalized chart filters actually applied to the query.",
+          "type": "object"
+        },
+        "subtitle": {
+          "description": "Display subtitle describing the filters.",
+          "type": "string"
+        },
+        "summary": {
+          "additionalProperties": false,
+          "properties": {
+            "periods": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "series": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "total": {
+              "description": "Total or average across returned points.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "total",
+            "periods",
+            "series"
+          ],
+          "type": "object"
+        },
+        "title": {
+          "description": "Display title for the chart.",
+          "type": "string"
+        },
+        "unit": {
+          "description": "Unit used by point values and summary.total.",
+          "enum": [
+            "count",
+            "usd",
+            "percent"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "spec",
+        "title",
+        "subtitle",
+        "unit",
+        "points",
+        "summary"
+      ],
+      "type": "object"
+    },
+    "links": {
+      "additionalProperties": false,
+      "properties": {
+        "apiUrl": {
+          "description": "Chart JSON API URL.",
+          "type": "string"
+        },
+        "embedUrl": {
+          "description": "Embeddable chart URL.",
+          "type": "string"
+        },
+        "pageUrl": {
+          "description": "Public chart page URL.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "embedUrl",
+        "pageUrl",
+        "apiUrl"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "links"
+  ],
+  "type": "object"
+}

Changed1 schema field changedApr 15, 2026

addedInput schema / properties / issuer

Added value: +{
+  "enum": [
+    "all",
+    "exclude_spacs"
+  ],
+  "type": "string"
+}

Changed1 schema field changedApr 15, 2026

changedInput schema / properties / metric / enum

Previous value: -[
-  "gross_proceeds",
-  "prospectus_count",
-  "final_prospectus_count"
-]New value: +[
+  "gross_proceeds",
+  "prospectus_count",
+  "final_prospectus_count",
+  "day1_return_pct"
+]

First observedApr 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by disclosing quota limits and clamping behavior for anonymous requests, which are not captured by annotations.

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?

Two concise sentences with no fluff. The first sentence states core purpose and output, the second provides important usage guidance and limitations.

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

Completeness4/5

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

Given 9 optional parameters and an output schema, the description covers the tool's purpose, output, and key behavioral notes. It could mention default parameter behaviors briefly, but overall it's sufficiently complete.

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 coverage is 100%, so the schema already fully describes each parameter. The description does not add parameter-level details beyond schema. Baseline 3 is appropriate.

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 it builds an aggregated IPO chart and returns data plus URLs, using specific verbs and resource. It distinguishes itself from sibling tools (get_company, list_companies, list_news) by focusing on chart generation.

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 description explicitly recommends using this tool instead of hand-building chart URLs, and notes anonymous request limitations. While it doesn't exclude alternative tools among siblings, the context is clear.

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

All IPOGrid IPO Calendar & Filing Research tools Inspect

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

Need Help?