iposignal

Companies with SEC financials (free)

lookup_companies_with_financials

Read-onlyIdempotent

FREE. Directory of companies we hold SEC iXBRL financial statements for, optionally filtered by ticker or company name. Returns ticker, company, CIK, latest reported period and pre/post-IPO period counts — use it to find which tickers get_company_financials can return. Paged: limit (default 200, max 500) and offset; the response carries total and nextOffset (null on the last page).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size, 1-500. Defaults to 200.
`query`	No	Filter by ticker or company name (case-insensitive substring). Omit to list every covered company.
`offset`	No	Rows to skip. Pass the previous response's nextOffset to fetch the next page.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Companies we hold SEC iXBRL financials for.
`count`	No	Rows in this page.
`limit`	No	Page size.
`total`	No	Rows matching the query across all pages.
`offset`	No	Rows skipped.
`nextOffset`	No	Offset of the next page, or null on the last page.

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": {
+    "count": {
+      "description": "Rows in this page.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "data": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "cik": {
+                "description": "SEC Central Index Key.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "company": {
+                "description": "Registrant name.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "latestPeriodEnd": {
+                "description": "End date of the latest reported period, YYYY-MM-DD.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "postIpoCount": {
+                "description": "Reporting periods after the IPO.",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "preIpoCount": {
+                "description": "Reporting periods before the IPO.",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "symbol": {
+                "description": "Ticker.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Companies we hold SEC iXBRL financials for."
+    },
+    "limit": {
+      "description": "Page size.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "nextOffset": {
+      "description": "Offset of the next page, or null on the last page.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "offset": {
+      "description": "Rows skipped.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Rows matching the query across all pages.",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedSep 23, 2026

addedInput schema / properties / limit / description

Added value: +"Page size, 1-500. Defaults to 200."

addedInput schema / properties / offset / description

Added value: +"Rows to skip. Pass the previous response's nextOffset to fetch the next page."

addedInput schema / properties / query / description

Added value: +"Filter by ticker or company name (case-insensitive substring). Omit to list every covered company."

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 200,
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

AddedSep 23, 2026

TDQS

A4.7/5.0

Behavior5/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 non-redundant behavioral context: 'FREE', pagination mechanics with limit/offset, and that the response carries total and nextOffset (null on the last page). This gives the agent confidence in paging and cost expectations beyond the annotations.

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, zero filler. The front-loading is excellent: 'FREE' and the core purpose come first, followed by return fields and the sibling routing, then pagination details. Every sentence earns its place.

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?

For a read-only directory lookup with all parameters optional, complete schema descriptions, and an output schema present, the description fully covers what an agent needs to call it correctly. It explains the return fields, filtering, paging, and the relationship to get_company_financials. There are no notable gaps.

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 each parameter already described in detail (limit defaults, offset semantics, query case-insensitive substring). The description does not add new meaning beyond the schema; it mostly restates the pagination pattern that the offset schema already documents ('Pass the previous response's nextOffset...'). 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 states a specific verb+resource: 'Directory of companies we hold SEC iXBRL financial statements for...' and enumerates the exact return fields. It also distinguishes itself from the sibling get_company_financials by explaining it is the discovery tool for which tickers are available. This is exactly what an agent needs to differentiate it.

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?

The description explicitly says, 'use it to find which tickers get_company_financials can return,' giving a direct when-to-use instruction tied to a named alternative. This is clear routing with no ambiguity about when to invoke this tool versus its sibling.

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.