Skip to main content
Glama

SEC Dataset Statistics

sec_stats

Retrieve key statistics on SEC EDGAR filings including total counts, form type distribution, date range, and last update time. Free to use.

Instructions

Get statistics about the SEC filings dataset: total filings, form type breakdown, date range, and last updated timestamp. Free endpoint, no payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the sec_stats tool. Makes a GET request to /api/v1/sec/stats and returns the JSON response.
      async () => {
        const res = await apiGet<SecStatsResponse>("/api/v1/sec/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • TypeScript interface for the SEC stats API response schema.
    interface SecStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • Registration of the sec_stats tool with the MCP server, specifying it has no input parameters.
    server.registerTool(
      "sec_stats",
      {
        title: "SEC Dataset Statistics",
        description:
          "Get statistics about the SEC filings dataset: total filings, form type breakdown, " +
          "date range, and last updated timestamp. Free endpoint, no payment required.",
        inputSchema: {},
      },
      async () => {
        const res = await apiGet<SecStatsResponse>("/api/v1/sec/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • src/index.ts:13-40 (registration)
    Import of the registerSecTools function in the main entry point.
    import { registerSecTools } from "./tools/sec.js";
    import { registerPacerTools } from "./tools/pacer.js";
    import { registerWeatherTools } from "./tools/weather.js";
    import { registerOtcTools } from "./tools/otc.js";
    import { registerTrademarkTools } from "./tools/trademarks.js";
    import { registerPatentTools } from "./tools/patents.js";
    import { registerCompanyTools } from "./tools/company.js";
    import { registerCryptoTools } from "./tools/crypto.js";
    import { registerSanctionsTools } from "./tools/sanctions.js";
    import { registerWhaleTools } from "./tools/whales.js";
    import { registerLabelTools } from "./tools/labels.js";
    import { registerHolderTools } from "./tools/holders.js";
    import { registerDexTools } from "./tools/dex.js";
    import { registerContractTools } from "./tools/contracts.js";
    import { registerPmTools } from "./tools/pm.js";
    import { registerPmArbTools } from "./tools/pm_arb.js";
    import { registerPmResolutionTools } from "./tools/pm_resolution.js";
    import { registerEconTools } from "./tools/econ.js";
    import { registerPmMicroTools } from "./tools/pm_micro.js";
    
    function createMcpServer() {
      const server = new McpServer({
        name: "verilex-data",
        version: "0.3.3",
      });
    
      registerNpiTools(server);
      registerSecTools(server);
  • src/index.ts:40-40 (registration)
    Registration call that wires sec_stats (and all other SEC tools) into the MCP server.
    registerSecTools(server);
Behavior3/5

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

No annotations provided, description only states it returns statistics and is free. Does not discuss rate limits, data freshness, or error conditions. Adequate for a simple stats endpoint but could be more transparent.

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 concise sentences, front-loads purpose and includes practical info about being free. No wasted words.

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

Completeness5/5

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

Given no parameters and no output schema, description adequately lists what statistics are returned (total filings, form breakdown, date range, timestamp). Serves its purpose for a simple stats endpoint.

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?

No parameters exist, so baseline is 4. Description adds meaning by explaining what the output contains, which is sufficient for parameter semantics.

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?

Clearly states it provides statistics about SEC filings dataset including specific items (total filings, form type breakdown, date range, timestamp). Distinguishes from siblings like search_sec_filings and get_sec_filing which are for individual filings.

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?

Mentions it's a free endpoint with no payment required, but does not explicitly state when to use compared to other SEC tools or when not to use. The usage is implied as a quick overview tool.

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