Skip to main content

FilingDelta

by xyz.filingdelta

Overview Discussions Admin

SEC filing diff card (paid $0.01)

get_filing_delta

Read-onlyIdempotent

Paid $0.01 USDC on Base. Call when you need what changed in a company's latest SEC filing (10-Q, 10-K, 8-K or 6-K) vs the prior period, not the headline: each change cited to EDGAR with a materiality rating and why it matters. Free: sample_delta. Tickers: AMD, MRVL, NVDA, AVGO, TSM, MU, AMAT, AAPL, MSFT, META, TSLA, ORCL, INTC, ASML, MSTR, JPM, BAC, GS, WFC, NFLX, JNJ, BRK, PLTR, SPCX, GOOGL, LLY, LRCX, BA. Others return 404 (no charge).

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Ticker

Output Schema

Name	Required	Description	Default
`period`	No
`ticker`	Yes
`changes`	Yes
`company`	No
`accession`	No
`period_end`	No
`source_url`	Yes
`filing_date`	No
`filing_type`	Yes
`generated_at`	No
`comparison_basis`	No
`high_materiality_count`	No
`new_material_items_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / ticker / enum

Previous value: -[
-  "AMD",
-  "MRVL",
-  "NVDA",
-  "AVGO",
-  "TSM",
-  "MU",
-  "AMAT",
-  "AAPL",
-  "MSFT",
-  "META",
-  "TSLA",
-  "ORCL",
-  "INTC",
-  "ASML",
-  "MSTR",
-  "JPM",
-  "BAC",
-  "GS",
-  "WFC",
-  "NFLX",
-  "JNJ",
-  "BRK",
-  "PLTR",
-  "SPCX"
-]New value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC",
+  "GS",
+  "WFC",
+  "NFLX",
+  "JNJ",
+  "BRK",
+  "PLTR",
+  "SPCX",
+  "GOOGL",
+  "LLY",
+  "LRCX",
+  "BA"
+]

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / ticker / enum

Previous value: -[
-  "AMD",
-  "MRVL",
-  "NVDA",
-  "AVGO",
-  "TSM",
-  "MU",
-  "AMAT",
-  "AAPL",
-  "MSFT",
-  "META",
-  "TSLA",
-  "ORCL",
-  "INTC",
-  "ASML",
-  "MSTR",
-  "JPM",
-  "BAC",
-  "GS",
-  "WFC",
-  "NFLX",
-  "JNJ",
-  "BRK",
-  "PLTR"
-]New value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC",
+  "GS",
+  "WFC",
+  "NFLX",
+  "JNJ",
+  "BRK",
+  "PLTR",
+  "SPCX"
+]

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / ticker / enum

Previous value: -[
-  "AMD",
-  "MRVL",
-  "NVDA",
-  "AVGO",
-  "TSM",
-  "MU",
-  "AMAT",
-  "AAPL",
-  "MSFT",
-  "META",
-  "TSLA",
-  "ORCL",
-  "INTC",
-  "ASML",
-  "MSTR",
-  "JPM",
-  "BAC",
-  "GS",
-  "WFC",
-  "NFLX",
-  "JNJ"
-]New value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC",
+  "GS",
+  "WFC",
+  "NFLX",
+  "JNJ",
+  "BRK",
+  "PLTR"
+]

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / ticker / enum

Previous value: -[
-  "AMD",
-  "MRVL",
-  "NVDA",
-  "AVGO",
-  "TSM",
-  "MU",
-  "AMAT",
-  "AAPL",
-  "MSFT",
-  "META",
-  "TSLA",
-  "ORCL",
-  "INTC",
-  "ASML",
-  "MSTR",
-  "JPM",
-  "BAC",
-  "GS",
-  "WFC",
-  "NFLX"
-]New value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC",
+  "GS",
+  "WFC",
+  "NFLX",
+  "JNJ"
+]

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / ticker / enum

Previous value: -[
-  "AMD",
-  "MRVL",
-  "NVDA",
-  "AVGO",
-  "TSM",
-  "MU",
-  "AMAT",
-  "AAPL",
-  "MSFT",
-  "META",
-  "TSLA",
-  "ORCL",
-  "INTC",
-  "ASML",
-  "MSTR",
-  "JPM",
-  "BAC",
-  "GS",
-  "WFC"
-]New value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC",
+  "GS",
+  "WFC",
+  "NFLX"
+]

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / ticker / enum

Previous value: -[
-  "AMD",
-  "MRVL",
-  "NVDA",
-  "AVGO",
-  "TSM",
-  "MU",
-  "AMAT",
-  "AAPL",
-  "MSFT",
-  "META",
-  "TSLA",
-  "ORCL",
-  "INTC",
-  "ASML",
-  "MSTR",
-  "JPM",
-  "BAC"
-]New value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC",
+  "GS",
+  "WFC"
+]

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / ticker / description
```
Added value: +"Ticker"
```

addedInput schema / properties / ticker / enum

Added value: +[
+  "AMD",
+  "MRVL",
+  "NVDA",
+  "AVGO",
+  "TSM",
+  "MU",
+  "AMAT",
+  "AAPL",
+  "MSFT",
+  "META",
+  "TSLA",
+  "ORCL",
+  "INTC",
+  "ASML",
+  "MSTR",
+  "JPM",
+  "BAC"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "accession": {
+      "type": "string"
+    },
+    "changes": {
+      "type": "array"
+    },
+    "company": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "comparison_basis": {
+      "type": "string"
+    },
+    "filing_date": {
+      "type": "string"
+    },
+    "filing_type": {
+      "type": "string"
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "high_materiality_count": {
+      "type": "number"
+    },
+    "new_material_items_count": {
+      "type": "number"
+    },
+    "period": {
+      "type": "string"
+    },
+    "period_end": {
+      "type": "string"
+    },
+    "source_url": {
+      "type": "string"
+    },
+    "ticker": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ticker",
+    "filing_type",
+    "source_url",
+    "changes"
+  ],
+  "type": "object"
+}

First observedOct 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds valuable behavioral context beyond the annotations: the $0.01 USDC cost on Base and the fact that unsupported tickers return 404 with no charge. It does not detail the payment flow, but the output schema covers return structure.

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 front-loaded with payment and use-case context, then supported tickers and error behavior. It is mostly efficient, though the long ticker enumeration duplicates the schema enum and adds some length.

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 presence of an output schema and annotations, the description is complete enough for correct invocation: it covers cost, intended use, distinction from headline data, free alternative, supported universe, and unsupported-ticker behavior.

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?

The single ticker parameter has 100% schema description coverage and an enum, so the schema carries the basic meaning. The description adds useful semantics beyond the schema by listing the supported tickers and specifying that others return 404 with no charge, even though the ticker list partially duplicates the enum.

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 states a specific verb and resource: it returns what changed in a company's latest SEC filing versus the prior period. It explicitly distinguishes the output from 'the headline' and points to the free sibling sample_delta, so an agent can identify the tool's role without opening the schema.

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?

It gives explicit when-to-use guidance ('Call when you need what changed...') and when-not guidance ('not the headline'), plus a named alternative for free sampling: sample_delta. This leaves little inference required for tool selection.

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

All FilingDelta tools Inspect

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

Need Help?