Skip to main content
Glama

Sec Search Companies

sec_search_companies
Read-onlyIdempotent

Search SEC EDGAR for companies by name or ticker symbol. Returns matching company names and their CIK numbers, which are needed for other SEC tools.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Apple"
    },
    "name": "sec_search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany name or ticker to search for (e.g., "Apple", "TSLA", "Microsoft")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / oneOf
      Added value: +[
      +  {
      +    "properties": {
      +      "companies": {
      +        "description": "List of matching companies",
      +        "items": {
      +          "properties": {
      +            "category": {
      +              "description": "Company category or type",
      +              "type": "string"
      +            },
      +            "cik": {
      +              "description": "Company CIK number (entity ID)",
      +              "type": "string"
      +            },
      +            "name": {
      +              "description": "Company name",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "category"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "found": {
      +        "description": "Present and true on an answer; a miss is the found:false branch.",
      +        "enum": [
      +          true
      +        ],
      +        "type": "boolean"
      +      },
      +      "query": {
      +        "description": "The search query used",
      +        "type": "string"
      +      },
      +      "total_hits": {
      +        "description": "Total number of matching results from SEC EDGAR",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "query",
      +      "total_hits",
      +      "companies"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "description": "A miss or an unavailable upstream: found:false with a reason and a hint (the shape check-found-false-schemas.mjs expects).",
      +    "properties": {
      +      "found": {
      +        "enum": [
      +          false
      +        ],
      +        "type": "boolean"
      +      }
      +    },
      +    "required": [
      +      "found"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "companies": {
      -    "description": "List of matching companies",
      -    "items": {
      -      "properties": {
      -        "category": {
      -          "description": "Company category or type",
      -          "type": "string"
      -        },
      -        "cik": {
      -          "description": "Company CIK number (entity ID)",
      -          "type": "string"
      -        },
      -        "name": {
      -          "description": "Company name",
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "category"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "query": {
      -    "description": "The search query used",
      -    "type": "string"
      -  },
      -  "total_hits": {
      -    "description": "Total number of matching results from SEC EDGAR",
      -    "type": "number"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "query",
      -  "total_hits",
      -  "companies"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / properties / companies / items / required
      Previous value: -[
      -  "cik",
      -  "name",
      -  "category"
      -]New value: +[
      +  "category"
      +]
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuine workflow context by explaining that CIKs are the keys consumed by other SEC tools, but says nothing about match behavior (exact vs partial), result limits, or ranking ambiguity.

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 short sentences, front-loaded with the action and scoped with the identifier types. Every sentence carries information an agent needs; nothing is redundant filler.

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 one-parameter read-only lookup with full schema coverage, annotations, and an output schema, the description covers purpose, output meaning, and downstream workflow fit. The only notable gap is match semantics (partial vs exact, how many results return), which matters for interpreting a search.

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% and the single parameter already documents that a company name or ticker is accepted with examples. The description restates that duality without adding format rules, minimum query length, or ambiguity handling, so it meets the baseline but adds no new meaning.

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 (search) and resource (SEC EDGAR companies) plus the accepted identifiers (name or ticker), and clarifies the output (names + CIK numbers). It implicitly separates itself from sec_get_company_facts by framing this as the CIK-lookup prerequisite, but never names a sibling alternative outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'which are needed for other SEC tools' signals this is the first step in a SEC workflow. There is no explicit when-to-use/when-not-to-use guidance and no stated alternative for resolving a company.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.