FinBridge

Search SEC EDGAR Companies

search_edgar_company

Read-only

Search SEC EDGAR registrants (US-listed companies) by ticker, company name, or CIK. Returns the 10-digit zero-padded CIK needed by the other edgar_* tools.

Not this tool for: Korean companies (use search_dart_company). Japan, Taiwan and Europe have no search tool — reach them through query_db on the companies table.

Args:

query (required): ticker ('AAPL', 'BRK-B' or 'BRK.B'), company-name fragment ('Berkshire'), or CIK number ('320193')
limit: max results, 1-50 (default 10)

Returns: {count, companies: [{cik, ticker, title}]} ranked exact-ticker > exact-name > prefix > substring.

Examples:

"find Apple's CIK" -> {query: 'AAPL'}
"companies named Berkshire" -> {query: 'Berkshire', limit: 5}

Use when: you need a CIK or to disambiguate a company name before calling get_edgar_financials/filings/insider_trades (those also accept tickers directly, so for an exact ticker you can skip this step). Don't use for: Korean companies (use search_dart_company) or private companies not registered with the SEC.

Errors: no match -> error suggesting a shorter name fragment; only SEC registrants with a listed ticker are searchable.

Input Schema

Name	Required	Description	Default
`limit`	No	Max matches to return (default 10)
`query`	Yes	Ticker (e.g. 'AAPL', 'BRK-B'), company-name fragment (e.g. 'Berkshire'), or CIK number

Output Schema

Name	Required	Description	Default
`count`	Yes
`companies`	Yes
`data_as_of`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
changedOutput schema / properties / companies / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / companies / items / properties / title / $ref
```
Removed value: -"#/properties/companies/items/properties/ticker"
```
addedOutput schema / properties / companies / items / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / data_as_of / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedNov 2, 2026

addedOutput schema / properties / data_as_of

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedSep 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint), and the description adds genuine behavioral context on top: the exact return shape and ranking order (exact-ticker > exact-name > prefix > substring), error behavior on no match, and the coverage limit that only ticker-listed SEC registrants are searchable.

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?

Well front-loaded with labeled sections (Args, Returns, Examples, Use when, Don't use for, Errors) that make it scannable. Minor redundancy: the Korean-company exclusion is stated twice, in both the opening "Not this tool for" block and the later "Don't use for" line.

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?

Complete for a two-parameter search tool: inputs, output shape, ranking, error paths, sibling routing, and the downstream CIK handoff to get_edgar_financials/filings/insider_trades are all covered. An output schema exists, so the return description is a bonus rather than a requirement.

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 baseline is 3, but the description adds real meaning beyond the schema by showing accepted ticker variants ('BRK-B' or 'BRK.B') and a concrete CIK example ('320193'), which the schema does not cover. The limit parameter's 1-50 bound is only restated, not enriched.

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?

States a specific verb and resource ("Search SEC EDGAR registrants") plus the accepted lookup keys (ticker, name, CIK), and immediately distinguishes itself from the sibling search_dart_company. An agent can identify the tool and its scope without opening the schema.

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?

Provides explicit "Use when" and "Don't use for" sections, names alternatives (search_dart_company for Korea, query_db for Japan/Taiwan/Europe), and adds the key optimization that an exact ticker can skip this step entirely since get_edgar_* accept tickers directly.

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

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