IPOGrid IPO Calendar & Filing Research

List News

list_news

Read-onlyIdempotent

List recent IPO-company news, optionally filtered by SEC CIK. Use this for a news feed; use get_company with news for broader issuer context. Anonymous requests return at most 10 rows and omit full content.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	Optional SEC CIK filter, with or without leading zeroes.
`limit`	No	Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10.
`cursor`	No	Opaque next_cursor from a previous response. Omit for the first page.
`include`	No	Set to ["content"] for stored article body text. Anonymous requests omit content.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Rows for the current page.
`meta`	Yes
`has_more`	Yes	Whether another page is available.
`next_cursor`	Yes	Opaque cursor for the next page, or null when this is the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 16, 2026

addedInput schema / properties / cik / description

Added value: +"Optional SEC CIK filter, with or without leading zeroes."

addedInput schema / properties / cursor / description

Added value: +"Opaque next_cursor from a previous response. Omit for the first page."

addedInput schema / properties / include / description

Added value: +"Set to [\"content\"] for stored article body text. Anonymous requests omit content."

addedInput schema / properties / limit / description

Added value: +"Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Rows for the current page.",
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "description": "Whether another page is available.",
+      "type": "boolean"
+    },
+    "meta": {
+      "additionalProperties": false,
+      "properties": {
+        "count": {
+          "description": "Number of rows returned in this page.",
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "count"
+      ],
+      "type": "object"
+    },
+    "next_cursor": {
+      "description": "Opaque cursor for the next page, or null when this is the last page.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "data",
+    "next_cursor",
+    "has_more",
+    "meta"
+  ],
+  "type": "object"
+}

First observedApr 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Discloses anonymous behavior (capped at 10 rows, no content) beyond annotations. Annotations already mark it as read-only, idempotent, and non-destructive, so no contradiction.

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?

Three short, front-loaded sentences covering purpose, usage guidance, and a behavioral quirk. No fluff.

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?

Covers main behavior, filtering, pagination (cursor), and authentication differences. Output schema exists so return values are not needed. Could mention time range for 'recent', but overall 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 description coverage is 100%, so baseline is 3. Description adds little beyond what schema already provides (e.g., 'optionally filtered by SEC CIK' is redundant). Does not enhance parameter understanding significantly.

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?

Clearly states 'List recent IPO-company news' with optional CIK filter. Explicitly distinguishes from sibling tools (get_company) by advising to use it for broader issuer context.

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

Usage Guidelines5/5

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

Provides when-to-use ('for a news feed') and when-not-to-use ('use get_company with news for broader issuer context'). Also notes anonymous request limitations (10 rows, no content).

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?