Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewAdmin

Edgar Company Filings

edgar_company_filings
Read-onlyIdempotent

AUTHORITATIVE list of recent SEC filings for a specific US public company. Pass a ticker ("AAPL") or CIK ("320193"). Filter by form type — "10-K" (annual report), "10-Q" (quarterly), "8-K" (material event — but for severity-classified 8-Ks specifically, prefer sec_8k_recent), "DEF 14A" (proxy), "S-1" (IPO registration), etc. Returns filing dates, form types, accession numbers, document links. Use for "what did $TICKER recently file" or "show me the last N proxy statements for $TICKER". For specific financial metrics over time use edgar_company_concept; for the full XBRL dump use edgar_company_facts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax filings to return (1-40, default 20)
form_typeNoFilter by SEC form type (e.g., "10-K", "10-Q", "8-K"). Omit for all types.
ticker_or_cikYesTicker symbol (e.g., "AAPL") or CIK number (e.g., "320193")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikYesCompany CIK number
filingsYes
tickersYesAssociated ticker symbols
company_nameYesOfficial company name
fiscal_year_endYesFiscal year end date
sic_descriptionYesStandard Industrial Classification description
filter_form_typeYesForm type filter applied or 'all'
state_of_incorporationYesState where company is incorporated

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cik": {
+      "description": "Company CIK number",
+      "type": "string"
+    },
+    "company_name": {
+      "description": "Official company name",
+      "type": "string"
+    },
+    "filings": {
+      "items": {
+        "properties": {
+          "accession_number": {
+            "description": "SEC accession number",
+            "type": "string"
+          },
+          "document_url": {
+            "description": "URL to access the filing document",
+            "type": "string"
+          },
+          "filing_date": {
+            "description": "Date filing was submitted",
+            "type": "string"
+          },
+          "form": {
+            "description": "SEC form type",
+            "type": "string"
+          },
+          "primary_document": {
+            "description": "Primary document filename",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "filter_form_type": {
+      "description": "Form type filter applied or 'all'",
+      "type": "string"
+    },
+    "fiscal_year_end": {
+      "description": "Fiscal year end date",
+      "type": "string"
+    },
+    "sic_description": {
+      "description": "Standard Industrial Classification description",
+      "type": "string"
+    },
+    "state_of_incorporation": {
+      "description": "State where company is incorporated",
+      "type": "string"
+    },
+    "tickers": {
+      "description": "Associated ticker symbols",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "cik",
+    "company_name",
+    "tickers",
+    "sic_description",
+    "state_of_incorporation",
+    "fiscal_year_end",
+    "filter_form_type",
+    "filings"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "form_type": "10-Q",
+    "limit": 15,
+    "ticker_or_cik": "AAPL"
+  },
+  {
+    "limit": 20,
+    "ticker_or_cik": "320193"
+  }
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds what the tool returns (filing dates, form types, accession numbers, document links), which is not in annotations. No contradictions; the description enhances transparency.

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 well-structured sentences plus a concise list of form type explanations. Front-loaded with the main purpose. Every sentence adds value; no fluff.

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?

Covers all necessary context: what the tool does, input parameters with examples, acceptable values for form_type with explanations, return fields, and references to related tools for other needs. Annotations cover safety; description fills remaining gaps.

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?

Input schema covers all 3 parameters with descriptions (100% coverage). The description adds meaning beyond schema by explaining form type values (e.g., '10-K' is annual report) and providing usage examples. This enriches the schema information, justifying above baseline.

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 verb (list), resource (SEC filings), and scope (specific US public company). It distinguishes from sibling tools by mentioning alternatives for other use cases (edgar_company_concept, edgar_company_facts, sec_8k_recent). The term 'AUTHORITATIVE' reinforces its unique role.

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

Usage Guidelines5/5

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

Explicitly states when to use (e.g., 'what did $TICKER recently file') and when not to use (e.g., financial metrics use edgar_company_concept). It also recommends a specific sibling (sec_8k_recent) for severity-classified 8-Ks, providing clear decision guidance.

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

All Edgar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources