Skip to main content
Glama

capabilities

by com.eckari
OverviewDiscussionsAdmin

Latest 10-K, 10-Q or 8-K for a US company by ticker or CIK

company_us_filings_latest
Read-onlyIdempotent

Give a stock ticker (AAPL) or CIK and get the most recent EDGAR filing of each requested form — by default the latest 10-K, 10-Q and 8-K — with filing and report dates and a direct sec.gov link to each primary document. Use when: What is Apple's latest 8-K, and where is the document? Not for: You need to know who submitted the filing — EDGAR's submissions index carries no filer identity, and for ownership forms (3, 4, 5, SCHEDULE 13G) the submitter is a third party, not the company. Price: USD 0.003/call (x402), 0.002 (account key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSEC CIK or exchange ticker symbol. All digits is read as a CIK (leading zeros and an EDGAR CIK prefix are both accepted: 320193, 0000320193, CIK0000320193); anything else is read as a ticker (1-10 characters starting with a letter) and matched exactly, case-insensitively, against the SEC listed-security index — AAPL, aapl and BRK-B all work. Company names are not accepted: resolve one with company.us.resolve. A ticker with no SEC index entry returns NOT_FOUND, which is not a billable result.
formNoComma-separated EDGAR form types to report the latest filing of. Defaults to "10-K,10-Q,8-K". Matching is exact and case-insensitive; output order follows the requested order.10-K,10-Q,8-K

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesCapability output; full JSON Schema at https://api.eckari.com/v1/capabilities/company.us.filings.latest
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / cik
      Removed value: -{
-  "description": "SEC Central Index Key, 1-10 digits, with or without leading zeros and with or without a CIK prefix. Obtain it from company.us.resolve.",
-  "maxLength": 13,
-  "minLength": 1,
-  "pattern": "^(?:[Cc][Ii][Kk])?[0-9]{1,10}$",
-  "type": "string"
-}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "SEC CIK or exchange ticker symbol. All digits is read as a CIK (leading zeros and an EDGAR CIK prefix are both accepted: 320193, 0000320193, CIK0000320193); anything else is read as a ticker (1-10 characters starting with a letter) and matched exactly, case-insensitively, against the SEC listed-security index — AAPL, aapl and BRK-B all work. Company names are not accepted: resolve one with company.us.resolve. A ticker with no SEC index entry returns NOT_FOUND, which is not a billable result.",
+  "maxLength": 13,
+  "minLength": 1,
+  "pattern": "^(?:(?:[Cc][Ii][Kk])?[0-9]{1,10}|[A-Za-z][A-Za-z0-9.-]{0,9})$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cik"
-]New value: +[
+  "id"
+]
  2. Changed7 schema fields changed
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / data / description
      Added value: +"Capability output; full JSON Schema at https://api.eckari.com/v1/capabilities/company.us.filings.latest"
    • removedOutput schema / properties / data / properties
      Removed value: -{
-  "cik": {
-    "description": "SEC Central Index Key, zero-padded to 10 digits.",
-    "type": "string"
-  },
-  "latest": {
-    "description": "One entry per requested form that appears in EDGAR's recent window for this CIK, in the order the forms were requested. Forms with no filing in that window are omitted rather than returned empty. The window is the company's EDGAR index, so a requested ownership form (3, 4, 5, SCHEDULE 13G) returns the newest filing made about the company by a third party; EDGAR does not publish who submitted it.",
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "accession_number": {
-          "description": "EDGAR accession number in dashed form (e.g. 0000320193-25-000079).",
-          "type": "string"
-        },
-        "document_url": {
-          "description": "Direct https://www.sec.gov link to the primary document, or null when EDGAR reports no primary document.",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "filing_date": {
-          "description": "Date the filing was accepted by EDGAR (YYYY-MM-DD).",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "form": {
-          "description": "EDGAR form type exactly as filed.",
-          "type": "string"
-        },
-        "primary_document": {
-          "description": "File name — or path relative to the filing's EDGAR Archives directory, which older submissions use — of the filing's primary document. document_url is the resolved link; prefer it over building one from this value.",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "report_date": {
-          "description": "Period or event date the filing reports on (YYYY-MM-DD), or null when the form has none.",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "form",
-        "accession_number",
-        "filing_date",
-        "report_date",
-        "primary_document",
-        "document_url"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "name": {
-    "description": "Current filer name on EDGAR.",
-    "type": "string"
-  }
-}
    • removedOutput schema / properties / data / required
      Removed value: -[
-  "cik",
-  "name",
-  "latest"
-]
    • addedOutput schema / properties / meta / properties / attribution_url
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • addedOutput schema / properties / meta / properties / retrieved_at / format
      Added value: +"date-time"
    • addedOutput schema / properties / meta / required
      Added value: +[
+  "capability",
+  "version",
+  "retrieved_at",
+  "source",
+  "freshness",
+  "request_id"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints, so the burden on the description is lighter. The description adds useful behavioral details: it returns filing and report dates, a direct sec.gov link, and notes that a ticker without SEC index entry returns NOT_FOUND as a non-billable result. It does not elaborate on pagination or result limits, but the output schema presumably covers the structure. This is strong beyond the annotations.

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?

The description is three sentences, front-loaded with the core function, then a usage guideline section, then pricing. Each sentence earns its place. It could drop the pricing line or move it to annotations, but it doesn't hurt clarity. Minor structural waste from the pricing sentence, which might be better as a note, but overall efficient.

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 the tool's moderate complexity, 100% schema coverage, and presence of an output schema, the description covers all essential aspects: what it does, how to use parameters, when to use it, behavioral quirks (CIK normalization, NOT_FOUND non-billable), and limitations (no filer identity). The output schema presumably documents the return structure, so no need to repeat it. Complete for an agent to confidently select and invoke.

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%, so baseline is 3. The description adds meaningful context beyond the schema: it explains how CIK prefixes and leading zeros are handled, that tickers are matched case-insensitively, that company names are not accepted (pointing to company_us_resolve), and the default form list. The form parameter gets clarity on matching and ordering. The extra explanations elevate this to a 4.

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 it retrieves the most recent EDGAR filings (10-K, 10-Q, 8-K) for a US company given a ticker or CIK, providing dates and direct sec.gov links. This is a specific verb+resource combination that distinguishes it from siblings like company_us_filings (which may retrieve historical filings) and company_us_resolve (which resolves company names).

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?

The description explicitly says 'Use when: What is Apple's latest 8-K, and where is the document?' and provides a clear 'Not for:' case explaining that it doesn't return filer identity and unsuitable for ownership forms. This gives direct when-to-use and when-not-to-use guidance, and implicitly steers users toward siblings like company_us_profile for other needs.

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

All capabilities toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources