Skip to main content
Glama
Sign In
secapi-mcp

secapi-mcp

Official
by secapi-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_companies

Find SEC-registered companies by name, ticker, or CIK. Retrieve entity metadata including company name, ticker, CIK, and entity type.

Instructions

Search SEC-registered companies by name, ticker, or CIK. Returns entity metadata including company name, ticker, CIK, and entity type.

Examples:

  • search_companies({ query: "Apple" })

  • search_companies({ ticker: "MSFT" })

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
cikNo
pageNo
limitNo
queryNo
tickerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided. Description implies read-only behavior but does not explicitly disclose safety, rate limits, or side effects. Adequate for a search tool but lacks full transparency.

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?

Description is concise with two short paragraphs. Front-loaded purpose. No extraneous text. Slightly more structure (e.g., parameter list) would improve usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, no output schema, and no annotations, the description is incomplete. Lacks explanation of required fields, error handling, pagination details, and output structure beyond basic fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Description partially explains query, ticker, cik parameters via examples but omits page and limit. Does not explain optionality or mutual exclusivity, leaving gaps beyond schema alone.

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?

Description clearly states verb 'search', resource 'SEC-registered companies', and specifies return fields (name, ticker, CIK, entity type). Distinct from sibling tools like search_filings or search_institutions.

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?

Description specifies search criteria (name, ticker, CIK) and provides examples, but does not explicitly differentiate from siblings like search_institutions or state when not to use.

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

Deploy Server

Other Tools