Stockfacts

Data coverage and freshness

get_data_coverage

Read-onlyIdempotent

What data Livermore has and how fresh it is: the Form 4 filing-date range, the 13F quarters loaded (with the number of filers), the latest complete 13F quarter, the number of curated superinvestors, the Schedule 13D, 13G and Form 144 filing-date ranges, the filing-date range of politicians' trade reports (the congress field: reports by members of the U.S. Congress), the last successful data updates (ISO 8601 UTC), the update schedule and the usage limits of this server. Call it to check whether a date or quarter is covered.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`f13`	Yes
`form4`	Yes
`limits`	Yes
`sources`	Yes
`website`	Yes
`congress`	Yes
`docs_url`	Yes
`ownership`	Yes
`llms_txt_url`	Yes
`superinvestors`	Yes
`update_schedule`	Yes
`last_successful_update`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 27, 2026

addedOutput schema / properties / congress

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "earliest_filed_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latest_filed_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "earliest_filed_date",
+    "latest_filed_date",
+    "note"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / last_successful_update / properties / congress
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / last_successful_update / required

Previous value: -[
-  "sec_filings",
-  "tickers",
-  "cusip_mapping"
-]New value: +[
+  "sec_filings",
+  "tickers",
+  "cusip_mapping",
+  "congress"
+]

removedOutput schema / properties / not_yet_available

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / ownership

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "form144": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "earliest_filed_date": {
+              "type": "string"
+            },
+            "latest_filed_at": {
+              "type": "string"
+            },
+            "latest_filed_date": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "earliest_filed_date",
+            "latest_filed_at",
+            "latest_filed_date"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "schedule_13d": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "earliest_filed_date": {
+              "type": "string"
+            },
+            "latest_filed_at": {
+              "type": "string"
+            },
+            "latest_filed_date": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "earliest_filed_date",
+            "latest_filed_at",
+            "latest_filed_date"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "schedule_13g": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "earliest_filed_date": {
+              "type": "string"
+            },
+            "latest_filed_at": {
+              "type": "string"
+            },
+            "latest_filed_date": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "earliest_filed_date",
+            "latest_filed_at",
+            "latest_filed_date"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "schedule_13d",
+    "schedule_13g",
+    "form144",
+    "note"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "website",
-  "sources",
-  "form4",
-  "f13",
-  "superinvestors",
-  "last_successful_update",
-  "update_schedule",
-  "not_yet_available",
-  "limits",
-  "docs_url",
-  "llms_txt_url"
-]New value: +[
+  "website",
+  "sources",
+  "form4",
+  "f13",
+  "superinvestors",
+  "ownership",
+  "congress",
+  "last_successful_update",
+  "update_schedule",
+  "limits",
+  "docs_url",
+  "llms_txt_url"
+]

First observedSep 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld=false, so the safety profile is covered. The description goes further by disclosing what the response contains (last successful updates, update schedule, server usage limits), which is genuine behavioral context an agent needs, though it says nothing about response size or rate limits on the call itself.

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?

One dense enumeration sentence followed by a short usage imperative — front-loaded and functional, though the field list is long and could be trimmed since an output schema exists. No filler or repetition.

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?

For a parameterless read-only inventory tool with an output schema, the description fully covers scope (which datasets), freshness semantics (ISO 8601 UTC update timestamps), and the decision it supports. Nothing needed to invoke it correctly is absent.

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?

Zero parameters, so there is no parameter semantics to miss; baseline 4 applies. The description correctly signals this is a no-argument inventory call.

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 a concrete verb+resource: returns the server's data coverage and freshness, enumerated by dataset (Form 4, 13F quarters, 13D/13G/144, congress trades). This is clearly distinct from the sibling fetch tools like get_insider_trades or get_stock_13f_holders, which return records rather than coverage metadata.

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?

The closing sentence is an explicit call-to-action: 'Call it to check whether a date or quarter is covered.' This gives clear when-to-use context (validate coverage before querying), but names no alternative tool or when-not-to-use condition, so it stops short of the top band.

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

All Stockfacts tools Inspect

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

Need Help?