Skip to main content

FilingDelta

by xyz.filingdelta

Overview Discussions Admin

Free sample filing-change card

sample_delta

Read-onlyIdempotent

Free sample of get_filing_delta for any covered ticker, no payment: one change in full (as in the paid card) and every other change as a teaser with category, section and materiality, plus direction, a size bucket and magnitude_basis (what the bucket measures, e.g. single_level) where the paid figures give them. Also hidden counts, gated_fields and buy_with. Use it to test before paying. 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.

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/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, closed read. The description adds real behavioral context they cannot carry: no payment required, only one change is complete, the rest are gated teasers, and hidden counts/gated_fields/buy_with are surfaced. It does not state rate limits or how partial results are flagged in the payload, so it falls short of a 5.

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?

The opening clause is well front-loaded, but the sentence is dense with nested jargon (magnitude_basis, size bucket, gated_fields, buy_with) and the 28-ticker enumeration duplicates the schema enum, consuming roughly a third of the text for zero informational gain.

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

Completeness4/5

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

With an output schema present and full annotations, the description needn't explain return shape, and it still covers the paywall/gating model and eligibility. It is essentially complete for an agent to call it correctly, with only the redundant ticker list and unexplained output field names as minor gaps.

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% and the single ticker parameter has a full enum, so the schema already does the work. The trailing ticker list restates the enum verbatim and adds no semantic meaning, leaving the baseline of 3 appropriate.

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?

States exactly what it is: a free sample of get_filing_delta, with one change returned in full and the rest as teasers. The name of the paid sibling is embedded, so an agent can distinguish this from get_filing_delta without opening either schema.

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

Usage Guidelines4/5

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

"Use it to test before paying" gives a clear selection context and implicitly routes production use to get_filing_delta. It stops short of an explicit exclusion (e.g. 'do not rely on this for full change data'), so the alternative is implied rather than spelled out.

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?