Skip to main content
Glama

Search SEC Companies

search_sec_companies

Search SEC-registered companies by name to retrieve CIK numbers, company names, and filing counts. Use the CIK to access company filings.

Instructions

Search for companies registered with the SEC by name. Returns CIK numbers, company names, and filing counts. Useful for finding a company's CIK before searching their filings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYesCompany name to search for (at least 2 characters)

Implementation Reference

  • The handler function for the 'search_sec_companies' tool. It takes a 'search' string input (min 2 chars), calls the Verilex API at /api/v1/sec/companies with the search parameter, and returns a formatted response listing matching SEC-registered companies with CIK numbers, names, and filing counts.
    server.registerTool(
      "search_sec_companies",
      {
        title: "Search SEC Companies",
        description:
          "Search for companies registered with the SEC by name. Returns CIK numbers, " +
          "company names, and filing counts. Useful for finding a company's CIK before " +
          "searching their filings.",
        inputSchema: {
          search: z
            .string()
            .min(2)
            .describe("Company name to search for (at least 2 characters)"),
        },
      },
      async ({ search }) => {
        const res = await apiGet<SecCompaniesResponse>("/api/v1/sec/companies", {
          search,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const summary = `Found ${count} compan${count === 1 ? "y" : "ies"}.`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • Input schema for the search_sec_companies tool. Uses Zod validation requiring a string with at least 2 characters.
      inputSchema: {
        search: z
          .string()
          .min(2)
          .describe("Company name to search for (at least 2 characters)"),
      },
    },
  • TypeScript interface for the response from the SEC companies API endpoint, used as a generic type parameter in the apiGet call.
    interface SecCompaniesResponse {
      dataset: string;
      count: number;
      data: Record<string, unknown>[];
    }
  • src/index.ts:40-40 (registration)
    Registration of all SEC tools (including search_sec_companies) by calling registerSecTools(server) in the main server setup.
    registerSecTools(server);
Behavior3/5

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

No annotations are present, so the description carries the full burden. It states the tool returns CIK numbers, company names, and filing counts, but does not disclose pagination, rate limits, result limits, or error handling. This is a moderate gap.

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?

The description consists of two concise sentences. The first states the action and outputs, the second provides a use case. No unnecessary words or repetition.

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 search tool with one parameter and no output schema, the description covers purpose, output content, and a typical use case. It could mention the format of results (e.g., list of matches) or behavior on no results, but it is largely complete.

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% for the single required 'search' parameter, with its description already explaining it takes a company name (min 2 chars). The tool description adds only 'by name', which is redundant. Baseline 3 applies.

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 clearly states the tool searches for SEC-registered companies by name and returns CIK numbers, company names, and filing counts. It distinguishes from sibling tools like search_sec_filings by explicitly noting it is for finding a CIK before searching filings.

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?

The description gives a specific use case (finding CIK before searching filings), implying when to use it. However, it does not explicitly state when not to use it or compare with alternatives like lookup_otc_ticker.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrierone/verilexdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server