EDGAR + Entity: US Company Research

Company profile (EDGAR)

get_company_profile

Read-onlyIdempotent

Company profile from SEC EDGAR submissions: legal name, tickers, exchanges, SIC code + industry, state of incorporation, fiscal year end, EIN, filer category, business/mailing addresses, former names, latest 10-K/10-Q. Use it to orient before deeper research.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "get_company_profile"
  }
}

Input Schema

Name	Required	Description	Default
`company`	Yes	Ticker (AAPL), CIK (320193 or 0000320193), or company name. Names must resolve unambiguously; use search_company first if unsure.

Output Schema

Name	Required	Description
`cik`	Yes
`sic`	No
`name`	No
`tickers`	No
`exchanges`	No
`source_url`	No
`former_names`	No
`fiscal_year_end`	No	MMDD
`sic_description`	No
`latest_annual_report`	No
`state_of_incorporation`	No
`latest_quarterly_report`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "cik": {
+      "type": "string"
+    },
+    "exchanges": {
+      "anyOf": [
+        {
+          "items": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "fiscal_year_end": {
+      "description": "MMDD",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "former_names": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "from": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "to": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "latest_annual_report": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "accession": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "filed": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "form": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "latest_quarterly_report": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "accession": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "filed": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "form": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sic": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sic_description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state_of_incorporation": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tickers": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "cik"
+  ],
+  "type": "object"
+}

First observedOct 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds that data is sourced from EDGAR submissions (implying externally-fetched, possibly stale data), but says nothing about lookup failure behavior, rate limits, or latency for an open-world network call.

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?

Two sentences, the field list front-loaded, and the usage hint trailing. No filler or redundancy.

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?

An output schema exists, so the enumerated return fields are a bonus rather than a necessity, and the required input is fully documented in the schema. What remains unaddressed is behavior on unresolvable names or EDGAR outages, a minor gap for a read-only profile tool.

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% and the single parameter's schema text already explains ticker/CIK/name forms and the search_company fallback. The description adds no parameter guidance beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Company profile from SEC EDGAR submissions') and enumerates the exact fields returned, so an agent knows precisely what it gets. It does not explicitly contrast itself with search_company or lookup_business_entity, so sibling differentiation is left implicit.

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?

'Use it to orient before deeper research' gives a clear contextual role for the tool relative to the deeper-research siblings. There are no explicit exclusions or named alternatives in the description itself (the search_company fallback lives in the schema, not here).

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

All EDGAR + Entity: US Company Research 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.