Skip to main content
Glama

SEC Filings Index

sv_filings
Read-only

Public-domain EDGAR filing metadata: filings_10k, filings_10q, filing_acceptance, report_calendar_us, sector_history — accession numbers, CIK, filing dates, document URLs, filing calendar, SIC sector classifications. Params: panel, ticker, start/end, limit (default 100, max 500). Free with X-ORKID-API-Key or $0.005 USDC/call via x402.

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": "sv_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date YYYY-MM-DD
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: filings_10k, filings_10q, filing_acceptance, report_calendar_us, sector_history
startNoStart date YYYY-MM-DD
tickerNoIssuer ticker, e.g. "AAPL"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / panel / description
      Previous value: -"Panel to query (default first). Available: filings_10k, filings_10q"New value: +"Panel to query (default first). Available: filings_10k, filings_10q, filing_acceptance, report_calendar_us, sector_history"
  2. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the description's job is added context, and it delivers: authentication via X-ORKID-API-Key or $0.005 USDC per call through x402, and that the underlying data is public domain. It does not mention rate limits, pagination behavior, or what a response envelope looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the resource, but it is written as a dash-separated catalog dump rather than prose, and the panel list plus limit default/max are repeated verbatim from the schema. Those duplicated tokens dilute rather than focus the description.

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

Completeness3/5

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

With no output schema, the description partially compensates by naming the returned field categories, and it discloses auth and cost. However it omits pagination/offset behavior, whether omitted dates mean unbounded range, and the cost/response shape distinction between panels, which matters for a 5-parameter broker-style tool.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all five parameters including the panel enum and the limit cap. The description only restates panel, ticker, start/end and the limit default/max without adding per-panel semantics such as whether ticker is meaningful for sector_history or report_calendar_us. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (public-domain EDGAR filing metadata) and enumerates the five panels and the fields returned (accession numbers, CIK, filing dates, document URLs, SIC sectors). An agent can tell it retrieves SEC filings rather than quotes or futures like the other sv_* siblings. It lacks an explicit verb, and it never distinguishes itself from sv_filing_sentiment, which is the closest-sounding sibling.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, even though sv_filing_sentiment sits right next to it in the namespace. The only routing hint is that panel defaults to the first available panel, which is usage-adjacent but not real guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources