Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sec_company_intelligence

Aggregate SEC company data into one call: profile, annual financial snapshot, latest 10-K/10-Q/8-K, and recent material events using CIK or ticker. Add market/news/hiring enrichment.

Instructions

Company 360 overview from SEC data. Aggregates a company's profile, a latest-annual financial snapshot, the latest 10-K/10-Q/8-K, and recent material events into one call. Provide cik or ticker. Optionally fuse live cross-source data with enrich (a comma list of market, news, hiring): market and news are keyed on the ticker; hiring needs ats plus that ATS's careers slug (or tenant/datacenter/site for Workday). Enrichment is best-effort — requested-but-unavailable sources are listed under degraded and never fail the SEC-native response.

Input Schema

NameRequiredDescriptionDefault
atsNoATS provider for hiring enrichment
cikNoSEC CIK (numeric or zero-padded)
siteNoWorkday career site (hiring, when ats=workday)
enrichNoComma list of cross-source enrichments
tenantNoWorkday tenant (hiring, when ats=workday)
tickerNoTicker symbol (alternative to cik)
datacenterNoWorkday datacenter shard (hiring, when ats=workday)
careers_slugNoCareers board slug for hiring (greenhouse/lever/ashby/smartrecruiters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / ats / enum
      Added value: +[
+  "greenhouse",
+  "lever",
+  "ashby",
+  "workday",
+  "smartrecruiters"
+]
    • addedInput schema / properties / enrich / enum
      Added value: +[
+  "market",
+  "news",
+  "hiring"
+]
  2. Addedv1.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it discloses important behavior: enrichment is best-effort, unavailable sources are reported under 'degraded', and enrichment failures never break the SEC-native response. It omits read-only/mutation clarity, auth needs, and rate limits, but the failure-mode disclosure is genuinely valuable.

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?

Dense and front-loaded: purpose first, then the input requirement, then the enrichment semantics and failure behavior. Every sentence carries information, though the enrichment clause is packed tightly enough to require careful reading.

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 an 8-param, no-annotation, no-output-schema tool the description covers the aggregation contents, the required input, and the enrichment contract well. It does not describe the shape of the returned data, but with no output schema that is a minor gap.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3), and the description adds real cross-parameter meaning beyond the schema: enrich=market/news key on ticker, while enrich=hiring requires ats plus the ATS's careers_slug (or tenant/datacenter/site for Workday). That dependency logic is not derivable from individual field descriptions.

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?

States a specific verb+resource (Company 360 overview from SEC data) and enumerates exactly what it aggregates: profile, latest-annual financial snapshot, latest 10-K/10-Q/8-K, and recent material events. This clearly differentiates it from the granular sec_financials/sec_filing siblings as a bundled overview.

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?

Tells the agent it must provide cik or ticker and that enrich is optional, giving clear usage context. It stops short of explicitly naming when to prefer this over sec_company_search or sec_financials, so it lacks true when-not guidance.

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