IPOGrid IPO Calendar & Filing Research

List Companies

list_companies

Read-onlyIdempotent

Discover IPOGrid companies and active deals with cursor pagination and market, issuer-kind, freshness, or proceeds filters. Use get_company after selecting an issuer. Anonymous requests return at most 10 rows and omit consensus enrichment.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Return only these issuer kinds. Omit to include every kind.
`limit`	No	Maximum rows to return. Defaults to 50 when authenticated; anonymous requests are capped at 10.
`scope`	No	Filter to IPO-only rows or all active deal rows.
`cursor`	No	Opaque next_cursor from a previous response. Omit for the first page.
`market`	No	Filter by normalized market family.
`include`	No	Optional enrichments for each row. Anonymous requests silently omit consensus.
`updated_since`	No	ISO-8601 lower bound on the company update timestamp.
`gross_proceeds_gt`	No	Lower bound on gross proceeds, using stated gross proceeds or a midpoint estimate from price range times shares offered.
`gross_proceeds_lt`	No	Upper bound on gross proceeds, using stated gross proceeds or a midpoint estimate from price range times shares offered.

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.

Changed6 schema fields changedJul 16, 2026

addedInput schema / properties / cursor / description

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

changedInput schema / properties / include / description

Previous value: -"Optional enrichments to include in each company row."New value: +"Optional enrichments for each row. Anonymous requests silently omit consensus."

changedInput schema / properties / kind / description

Previous value: -"Company kind filter."New value: +"Return only these issuer kinds. Omit to include every kind."

addedInput schema / properties / limit / description

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

changedInput schema / properties / updated_since / description

Previous value: -"ISO-8601 lower bound on companies.updated_at"New value: +"ISO-8601 lower bound on the company update timestamp."

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.2/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. Description adds context on anonymous request caps (10 rows) and omission of consensus enrichment, and mentions cursor pagination. No contradictions.

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 sentences: first covers purpose and filters, second guides usage and anonymous limits. No fluff, front-loaded with key info.

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?

For a complex tool with 9 parameters and output schema, the description covers purpose, pagination, filtering, and sibling guidance. Omits return format details, but output schema covers that.

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% with detailed parameter descriptions. The description summarizes filter categories (market, issuer-kind, freshness, proceeds) but does not add new meaning beyond the schema; baseline score of 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 uses a specific verb 'Discover' and resource 'IPOGrid companies and active deals', and distinguishes from sibling tool 'get_company' by stating 'Use get_company after selecting an issuer.'

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?

Explicitly advises using get_company for a specific company after listing, but does not address when to use alternatives like get_chart or list_news. Also mentions anonymous request limitations.

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?