iposignal

IPO overview (free)

get_ipo_overview

Read-onlyIdempotent

FREE. The public facts of an IPO: company, ticker, CIK, exchange, listing date, shares offered, price range, final offer price when the deal has priced, and gross proceeds. Use it to identify a deal before buying the full profile with get_ipo_snapshot. Provide exactly one of companyId, symbol, or cik.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ipo_overview"
  }
}

Input Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, with or without leading zeros, e.g. 1876042 or 0001876042.
`symbol`	No	US ticker symbol, e.g. CRCL. Case-insensitive. Tickers get reassigned, so a response may carry a symbolNote.
`companyId`	No	IPOSignal company id (24-character hex), as returned by other IPOSignal responses.

Output Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, 10 digits.
`venue`	No	Listing exchange.
`symbol`	No	Ticker.
`company`	No	Registrant name.
`premium`	No	What get_ipo_snapshot adds.
`ipoDetails`	No	Public deal facts: date, exchange, shares offered, priceRange, offerPrice (final terms only), offerSize (gross proceeds). No valuation.
`symbolNote`	No	Present only when the requested ticker is contested: which registrant it belongs to now vs. the record served.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "cik": {
+      "description": "SEC Central Index Key, 10 digits.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "company": {
+      "description": "Registrant name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ipoDetails": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Public deal facts: date, exchange, shares offered, priceRange, offerPrice (final terms only), offerSize (gross proceeds). No valuation."
+    },
+    "premium": {
+      "description": "What get_ipo_snapshot adds.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "symbol": {
+      "description": "Ticker.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "symbolNote": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present only when the requested ticker is contested: which registrant it belongs to now vs. the record served."
+    },
+    "venue": {
+      "description": "Listing exchange.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedSep 23, 2026

addedInput schema / properties / cik / description

Added value: +"SEC Central Index Key, with or without leading zeros, e.g. 1876042 or 0001876042."

addedInput schema / properties / companyId / description

Added value: +"IPOSignal company id (24-character hex), as returned by other IPOSignal responses."

addedInput schema / properties / symbol / description

Added value: +"US ticker symbol, e.g. CRCL. Case-insensitive. Tickers get reassigned, so a response may carry a symbolNote."

AddedSep 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context: the tool is FREE, returns only public facts, and notes that final offer price appears only 'when the deal has priced', which is a meaningful conditional behavior.

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 sentences with no filler: the first presents the value and scope, the second gives the routing guidance, and the third states the parameter constraint. Every sentence earns its place and is front-loaded with the key 'FREE' signal.

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

Completeness5/5

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

Given the rich input schema, clear annotations, output schema, and explicit sibling differentiation, the description provides everything an agent needs to select and invoke the tool correctly. It covers cost, scope, alternatives, and input constraints without needing to restate return values that the output schema already documents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter has a solid description, so the baseline is 3. The description adds value beyond the schema by stating the exclusivity requirement ('exactly one of companyId, symbol, or cik'), which the schema does not enforce since no parameters are required.

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 states a clear purpose: retrieving the public facts of an IPO, and enumerates the specific fields (company, ticker, CIK, exchange, listing date, shares, price range, final offer price, gross proceeds). It also distinguishes itself from get_ipo_snapshot by framing this as the free identification step before buying the full profile.

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?

Explicitly gives the usage context: use this tool to identify a deal before buying the full profile with get_ipo_snapshot. It also states the input constraint clearly ('Provide exactly one of companyId, symbol, or cik'), giving an agent actionable selection criteria.

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

All iposignal 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.