Skip to main content
Glama
Sign In

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Watchlist Diff

watchlist_diff
Read-onlyIdempotent

Return new SEC filings across a set of companies since a given date. Name the companies with name (one watchlist you have already saved), names (several saved watchlists scanned together, companies de-duplicated; a name that does not exist is listed in watchlists_not_found, not an error) OR tickers (a list you are holding right now) — pass exactly one of the three. Use tickers for an ad-hoc question: there is no need to create a watchlist just to ask, and you should not, because a saved watchlist is a durable record in the user's account. Reads filing.parquet — does not call insider/ratio surfaces (use those tools separately if you need them). Scans at most 50 companies per call and reports truncated when you asked about more; batch a large universe rather than relying on the cap. A company whose read fails is named in tickers_failed, never silently reported as having filed nothing. NOT point-in-time: since bounds filing_date, not accepted_at.

Input Schema

NameRequiredDescriptionDefault
nameNoName of a watchlist the caller has already saved. Pass exactly one of `name`, `names`, `tickers`.
namesNoNames of saved watchlists to scan together; their companies are de-duplicated. A name that is not found is skipped and listed in `watchlists_not_found`. Pass exactly one of `name`, `names`, `tickers`.
sinceYesCutoff date (YYYY-MM-DD); the diff returns SEC filings whose filing_date is on or after this date.
tickersNoTickers or CIKs to scan, passed directly. Use this for an ad-hoc question — do NOT create a watchlist in order to ask one, since that writes a durable record into the user's account. Pass exactly one of `name`, `names`, `tickers`.
form_typesNoFiling forms to include. Defaults to 10-K + 10-Q + 8-K.

Output Schema

NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
sinceYes
filingsYes
truncatedYes
tickers_failedYes
watchlist_nameYes
tickers_scannedYes
tickers_requestedYes
watchlists_not_foundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Name of a watchlist the caller has already saved. Pass this OR `tickers`, never both."New value: +"Name of a watchlist the caller has already saved. Pass exactly one of `name`, `names`, `tickers`."
    • addedInput schema / properties / names
      Added value: +{
+  "description": "Names of saved watchlists to scan together; their companies are de-duplicated. A name that is not found is skipped and listed in `watchlists_not_found`. Pass exactly one of `name`, `names`, `tickers`.",
+  "items": {
+    "maxLength": 80,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 25,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / tickers / description
      Previous value: -"Tickers or CIKs to scan, passed directly. Use this for an ad-hoc question — do NOT create a watchlist in order to ask one, since that writes a durable record into the user's account. Pass this OR `name`, never both."New value: +"Tickers or CIKs to scan, passed directly. Use this for an ad-hoc question — do NOT create a watchlist in order to ask one, since that writes a durable record into the user's account. Pass exactly one of `name`, `names`, `tickers`."
    • addedOutput schema / properties / watchlists_not_found
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "_meta",
-  "watchlist_name",
-  "since",
-  "tickers_scanned",
-  "tickers_requested",
-  "truncated",
-  "tickers_failed",
-  "filings"
-]New value: +[
+  "_meta",
+  "watchlist_name",
+  "watchlists_not_found",
+  "since",
+  "tickers_scanned",
+  "tickers_requested",
+  "truncated",
+  "tickers_failed",
+  "filings"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description
      Previous value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."
  3. Changed2 schema fields changed
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description
      Previous value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / billed / description
      Previous value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."
  4. Changed4 schema fields changed
    • addedOutput schema / properties / filings / items / properties / company_name
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / filings / items / properties / document_url
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / filings / items / properties / inline_viewer_url
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / filings / items / required
      Previous value: -[
-  "ticker",
-  "accession_id",
-  "form_type",
-  "filing_date",
-  "accepted_at",
-  "sec_url"
-]New value: +[
+  "ticker",
+  "company_name",
+  "accession_id",
+  "form_type",
+  "filing_date",
+  "accepted_at",
+  "sec_url",
+  "document_url",
+  "inline_viewer_url"
+]
  5. Added
  6. Removed
  7. Changed1 schema field changed
    • changedOutput schema / properties / _meta / properties / fundamentals_as_of / description
      Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."
  8. Changed9 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Watchlist name."New value: +"Name of a watchlist the caller has already saved. Pass this OR `tickers`, never both."
    • changedInput schema / properties / since / description
      Previous value: -"Cutoff date (YYYY-MM-DD); the diff returns SEC filings accepted on or after this date across the watchlist's tickers."New value: +"Cutoff date (YYYY-MM-DD); the diff returns SEC filings whose filing_date is on or after this date."
    • addedInput schema / properties / tickers
      Added value: +{
+  "description": "Tickers or CIKs to scan, passed directly. Use this for an ad-hoc question — do NOT create a watchlist in order to ask one, since that writes a durable record into the user's account. Pass this OR `name`, never both.",
+  "items": {
+    "maxLength": 10,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "since"
-]New value: +[
+  "since"
+]
    • addedOutput schema / properties / tickers_failed
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / tickers_requested
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / truncated
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / properties / watchlist_name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / required
      Previous value: -[
-  "_meta",
-  "watchlist_name",
-  "since",
-  "tickers_scanned",
-  "filings"
-]New value: +[
+  "_meta",
+  "watchlist_name",
+  "since",
+  "tickers_scanned",
+  "tickers_requested",
+  "truncated",
+  "tickers_failed",
+  "filings"
+]
  9. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / fundamentals_as_of
      Added value: +{
+  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+  "type": "string"
+}
    • addedOutput schema / properties / _meta / properties / price_as_of
      Added value: +{
+  "description": "ISO timestamp when the price surfaces were last refreshed.",
+  "type": "string"
+}
  10. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / cost_usd
      Added value: +{
+  "additionalProperties": false,
+  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+  "properties": {
+    "amount_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+      "enum": [
+        "payg_charge",
+        "payg_rate_card"
+      ],
+      "type": "string"
+    },
+    "billed": {
+      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "amount_usd",
+    "billed",
+    "basis"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / _meta / properties / latency_ms
      Added value: +{
+  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+  "minimum": 0,
+  "type": "integer"
+}
  11. Changed1 schema field changed
    • addedOutput schema / properties / _meta / properties / pit_safe / description
      Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
  12. Changed1 schema field changed
    • addedInput schema / properties / since / description
      Added value: +"Cutoff date (YYYY-MM-DD); the diff returns SEC filings accepted on or after this date across the watchlist's tickers."
  13. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only mark it read-only/idempotent/open-world; the description adds the operational facts that actually matter: a hard 50-company scan cap, a `truncated` flag, failed reads surfaced in `tickers_failed` instead of silently returning empty, nonexistent watchlist names going to `watchlists_not_found` rather than erroring, and the NOT point-in-time caveat that `since` bounds filing_date not accepted_at.

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?

Front-loaded with the action, then selector rules, then behavioral caveats; nearly every sentence carries distinct information. It is dense and long for one paragraph, but nothing is clearly redundant.

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?

Covers selector semantics, scan limits, partial-failure handling, and the point-in-time caveat, so an agent can call it correctly and interpret a sparse result. Output schema exists, so return-value detail is appropriately not restated.

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 still adds semantics by contrasting the selectors conceptually (a saved watchlist is 'a durable record in the user's account', `names` de-duplicates companies). It does not mention `form_types` defaulting behavior or the enum values, which the schema covers.

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?

Opens with a specific verb and resource: 'Return new SEC filings across a set of companies since a given date.' It scopes itself ('Reads filing.parquet — does not call insider/ratio surfaces') which separates it from insider/ratio siblings. It doesn't explicitly name the most confusable sibling (latest_filings), so a 4 rather than a 5.

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?

Explicit guidance on the three mutually exclusive selectors and when each applies: `tickers` for ad-hoc questions, `name`/`names` for saved watchlists, with a stated prohibition against creating a watchlist just to ask. It also says to batch a large universe rather than lean on the 50-company cap.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data 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