Skip to main content
Glama
SEC EDGAR MCP

SEC EDGAR MCP

by reblickulous

lookup_company

Search SEC EDGAR by company name or ticker to retrieve the CIK number and legal name, then use that CIK before searching filings.

Instructions

Search for a company on SEC EDGAR by name or ticker symbol. Returns CIK number and full legal name. Always run this first to get a CIK before searching filings.

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_name": "<company_name>"
    },
    "name": "lookup_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_nameYesCompany name or ticker to search for (e.g. 'Palantir Technologies' or 'PLTR')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states the data source (SEC EDGAR) and that it returns a CIK and legal name, but it does not describe read-only behavior, ambiguity handling, error conditions, or rate-limit considerations.

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 short sentences are front-loaded with the core action, followed by return values and the ordering prerequisite. There is no redundant or filler wording.

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?

For a simple one-parameter lookup with no output schema, the description explains what is searched, what is returned, and the key prerequisite for downstream filing searches. Minor gaps around error or ambiguity behavior remain, but the definition is largely complete for this tool's complexity.

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?

The input schema has 100% description coverage and already documents the single company_name parameter with examples for both a name and a ticker. The description restates that name or ticker may be used, adding little beyond the 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 states a specific verb and resource: search for a company on SEC EDGAR by name or ticker. It also names the return values (CIK and full legal name), making the purpose concrete and distinguishable from filing-search 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?

It gives clear ordering guidance: 'Always run this first to get a CIK before searching filings.' This tells the agent when the tool is needed as a prerequisite, although it does not explicitly name or compare against sibling tools or explain when not to use it.

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