iposignal

IPO market sentiment score (premium)

get_ipo_sentiment

Read-only

Access IPOSignal's proprietary market sentiment score — a daily signal quantifying how well recent IPOs are being received by investors. Ranges from -100 (extreme bearish) to +100 (extreme bullish) with trend data for the last N days. Use it to identify favorable IPO windows, time investment entries, and assess overall market appetite for new listings. PREMIUM: paid per call over x402 (USDC on Base); an unpaid call returns the payment terms, and a not-found is never charged. Same data and price as the HTTP endpoint /api/agent/ipo-sentiment.

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_sentiment"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Trend window in days, 1-90. Defaults to 14.

Output Schema

Name	Required	Description
`trend`	No	Daily readings, newest first.
`current`	No	Latest daily reading.
`summary`	No	One-line reading of level and direction.

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": {
+    "current": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "computedAt": {
+              "description": "ISO timestamp.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "date": {
+              "description": "YYYY-MM-DD.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "direction": {
+              "description": "bullish, bearish or neutral.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "reliable": {
+              "description": "False when the sample is too small to trust.",
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "sampleSize": {
+              "description": "IPOs the score is computed from.",
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "score": {
+              "description": "-100 (extreme bearish) to +100 (extreme bullish).",
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "strength": {
+              "description": "weak, moderate or strong.",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Latest daily reading."
+    },
+    "summary": {
+      "description": "One-line reading of level and direction.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "trend": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/properties/current/anyOf/0"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Daily readings, newest first."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 23, 2026
- addedInput schema / properties / days / description
```
Added value: +"Trend window in days, 1-90. Defaults to 14."
```
First observedMay 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the premium payment model (paid per call over x402), the unpaid call behavior (returns payment terms), and the not-found never being charged. It also mentions the data is the same as the HTTP endpoint. This goes beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise and front-loaded with the core purpose. It includes important usage context and payment terms. The sentence about premium payment is a bit long but necessary. Overall, every sentence earns its place, though it could be slightly more streamlined.

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?

The tool has a simple parameter set (1 optional param), an output schema exists, and annotations cover safety. The description covers the key behavioral aspects: premium pricing, unpaid call behavior, and the HTTP endpoint equivalence. It's complete enough for an agent to call correctly, though it doesn't describe the output structure in detail (but the output schema exists).

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 the schema already documents the 'days' parameter with its range and default. The description mentions 'trend data for the last N days' which aligns with the parameter, but doesn't add much beyond what the schema provides. 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 the tool's purpose: accessing IPOSignal's proprietary market sentiment score, a daily signal quantifying how well recent IPOs are received. It specifies the range (-100 to +100), trend data, and use cases. It distinguishes itself from siblings by focusing on market sentiment, not company financials or IPO events.

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 provides clear use cases: identify favorable IPO windows, time investment entries, and assess overall market appetite. It also mentions the premium payment model and the HTTP endpoint alternative. However, it doesn't explicitly state when to use this over get_ipo_social_sentiment, which is a sibling that might seem similar.

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.