Skip to main content
Glama

SEC filings (10-K, 10-Q, 8-K, etc)

filings
Read-only

SEC filings (10-K, 10-Q, 8-K, etc) (GET https://app.deepvalues.ai/api/v1/filings/{ticker}, e.g. https://app.deepvalues.ai/api/v1/filings/AAPL — 0.001 credits per call ($0.005 when paid per call over x402); works with no credentials up to 25 call(s)/day per address) Missing data? Call request_data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNo
limitNo
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / form / examples
      Added value: +[
      +  "10-K"
      +]
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description earns credit for disclosing cost (0.001 credits/call, $0.005 under x402 pay-per-call) and the credential-free quota of 25 calls/day per address — concrete constraints an agent cannot get from the annotations. It also flags a fallback path when the response lacks data. It stops short of describing what a filing record contains or how results are ordered.

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?

All content sits in one bloated parenthetical that shows both a URL template and an example URL, then stacks pricing, x402 pricing, and quota inside nested parentheses. The endpoint and example are somewhat redundant, and the most task-critical facts (cost, quota) are buried mid-sentence rather than front-loaded.

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 should say what comes back — filing form type, dates, document links — and it never does. It does cover the operational envelope (cost, auth, quota, missing-data fallback), which is meaningful for a read-only GET tool, but the response shape remains guesswork.

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

Parameters2/5

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

Schema coverage is only 33% — `ticker` is documented (including the path-substitution warning) but `form` and `limit` are bare in the schema. The description adds nothing about accepted form values or what `limit` (default 10, max 50) truncates, so it does not compensate for the coverage gap.

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

Purpose3/5

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

The description largely restates the title ("SEC filings (10-K, 10-Q, 8-K, etc)") and then gives the endpoint URL, from which the agent must infer that it retrieves filings for a ticker. The resource is identifiable, but no verb is stated and nothing distinguishes it from the sibling `as_filed`, which plausibly covers overlapping filing data.

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?

There is one explicit conditional route: "Missing data? Call `request_data`." That is real alternative guidance, but it addresses failure handling rather than when to choose this tool over `as_filed`, `fundamentals`, or `news`. Usage is only implied by the URL shape (single ticker, optional form filter).

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