iposignal

Live company valuation metrics (premium)

get_company_metrics

Read-only

Get live valuation metrics for any US-listed company (not just IPOs), computed from primary sources: SEC XBRL companyfacts TTM fundamentals (revenue, net income, EBITDA, debt, cash, shares) plus the latest market close. Returns multiples (P/E, P/S, EV/Revenue, EV/EBITDA), derivations (PEG, earnings/sales/EBITDA yields, net-debt/EBITDA), margins, and YoY growth — the same data IPOSignal's valuation pipeline uses for peer benchmarking, with the computation convention stated in the response. Provide exactly one of symbol (any SEC-mapped ticker) or companyName (resolves Nasdaq/NYSE 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/company-metrics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No	Any SEC-mapped US ticker, e.g. AAPL. Provide exactly one of symbol or companyName.
`companyName`	No	Company name, used when the ticker is unknown. Resolves Nasdaq/NYSE listings only.

Output Schema

TableJSON Schema

Name	Required	Description
`listing`	No	ticker, name, exchange, cik.
`profile`	No	Margins and YoY growth.
`sources`	No	Where each input came from.
`valuation`	No	marketCap, enterpriseValue, P/E, P/S, EV/Revenue, EV/EBITDA, PEG, yields, net-debt/EBITDA.
`convention`	No	How the figures were computed.
`priceClose`	No	Latest market close, USD.
`fundamentalsTtm`	No	Trailing-twelve-month revenue, net income, EBITDA, FCF, debt, cash, shares outstanding (and sharesSource), from SEC XBRL.

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": {
+    "convention": {
+      "description": "How the figures were computed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fundamentalsTtm": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Trailing-twelve-month revenue, net income, EBITDA, FCF, debt, cash, shares outstanding (and sharesSource), from SEC XBRL."
+    },
+    "listing": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "ticker, name, exchange, cik."
+    },
+    "priceClose": {
+      "description": "Latest market close, USD.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "profile": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Margins and YoY growth."
+    },
+    "sources": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Where each input came from."
+    },
+    "valuation": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "marketCap, enterpriseValue, P/E, P/S, EV/Revenue, EV/EBITDA, PEG, yields, net-debt/EBITDA."
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / companyName / description

Added value: +"Company name, used when the ticker is unknown. Resolves Nasdaq/NYSE listings only."

addedInput schema / properties / symbol / description

Added value: +"Any SEC-mapped US ticker, e.g. AAPL. Provide exactly one of symbol or companyName."

AddedJul 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description reveals meaningful behavioral details: data is computed from SEC XBRL companyfacts and the latest market close, the response includes the computation convention, and payment semantics are disclosed (paid per call, unpaid calls return payment terms, not-found is never charged). These details materially help an agent understand side effects and prerequisites.

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?

The description is dense but every sentence earns its place: purpose, data source, return content, parameter rule, pricing behavior, and HTTP equivalence. It is front-loaded with the core action and scope, then proceeds logically through outputs, usage, and operational details. There is no filler or redundant explanation.

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 the output schema exists, the description does not need to explain return values, and it covers source, computation, pricing, parameter constraints, and endpoint parity. It is slightly short on explicit sibling-tool selection guidance, such as when to prefer get_company_financials for raw statements, but the 'not just IPOs' contrast and the valuation-specific output list make the intended use clear. An agent has enough context to invoke it correctly.

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%, so the schema already documents both parameters well. The description adds the critical 'exactly one of symbol or companyName' constraint, which the schema does not enforce, and clarifies that symbol covers any SEC-mapped ticker while companyName resolves Nasdaq/NYSE listings. This is meaningful semantic guidance beyond the input schema.

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 opens with 'Get live valuation metrics for any US-listed company (not just IPOs)', which clearly states the verb, resource, and scope while distinguishing it from IPO-focused siblings. It further specifies the exact outputs (P/E, EV/Revenue, margins, growth, etc.), making it unambiguous what the tool does and how it differs from related tools.

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 gives clear context for when to use the tool: when live valuation metrics for any US-listed company are needed, and explicitly says it is not limited to IPOs. It also explains the mutually exclusive input choice between symbol and companyName, the premium pricing behavior, and parity with the HTTP endpoint. It does not explicitly name sibling tools as alternatives or state when not to use it, so it stops just short of full routing guidance.

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.