New Runtime public records

What is new on New Runtime

whats_new

Read-onlyIdempotent

Use for a quick feed of what New Runtime published in the last 1-14 days (news signals, analyses, field notes, weekly knowledge updates), newest first, at most 40 items with title, date, URL and a one-line why. Free, no auth. Example: {"days": 7, "kinds": ["signal", "analysis"]}. For what changed against what you already knew, use what_changed.

Input Schema

Name	Required	Description	Default
`days`	No	Look-back window in days.
`kinds`	No	Optional subset of kinds; default all.

Output Schema

Name	Required	Description
`days`	No	Window length in days.
`next`	No	Present when truncated: how to see the rest.
`count`	Yes	Items returned.
`items`	Yes	Newest first.
`kinds`	No	Kinds included.
`since`	Yes	Window start, YYYY-MM-DD.
`total`	Yes	Items in the window.
`until`	Yes	Window end, YYYY-MM-DD.
`truncated`	Yes	True when more than the cap matched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Items returned.",
+      "type": "number"
+    },
+    "days": {
+      "description": "Window length in days.",
+      "type": "number"
+    },
+    "items": {
+      "description": "Newest first.",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Record date, YYYY-MM-DD."
+          },
+          "json": {
+            "description": "Machine-readable twin of the page."
+          },
+          "kind": {
+            "description": "Record kind."
+          },
+          "title": {
+            "description": "Record title."
+          },
+          "url": {
+            "description": "newruntime.com page; pass it to get_record."
+          },
+          "why": {
+            "description": "One line on why the item matters."
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kinds": {
+      "description": "Kinds included.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next": {
+      "description": "Present when truncated: how to see the rest.",
+      "type": "string"
+    },
+    "since": {
+      "description": "Window start, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "total": {
+      "description": "Items in the window.",
+      "type": "number"
+    },
+    "truncated": {
+      "description": "True when more than the cap matched.",
+      "type": "boolean"
+    },
+    "until": {
+      "description": "Window end, YYYY-MM-DD.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "since",
+    "until",
+    "total",
+    "count",
+    "truncated",
+    "items"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 27, 2026
- addedInput schema / properties / days / examples
```
Added value: +[
+  7
+]
```
AddedSep 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already establish that this is a non-destructive, read-only, idempotent, closed-world operation. The description adds useful behavioral context beyond that: free access with no authentication, newest-first ordering, a maximum of 40 items, and the fields returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded: it starts with the use case, then adds scope, example, and alternative-tool routing. Every sentence carries useful selection or invocation information.

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?

This is a simple read-only feed with only two optional parameters, full schema coverage, annotations, and an output schema. The description supplies the remaining practical context an agent needs: auth cost, ordering, item cap, and when to prefer what_changed.

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 the input schema already documents both parameters thoroughly. The description still adds value by giving a concrete JSON example and illustrating the intended kind filters ('signal', 'analysis'), though it does not explain every enum value.

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: a quick feed of what New Runtime published. It also gives scope (1-14 days, content kinds, newest first, max 40 items) and explicitly distinguishes itself from the sibling tool what_changed.

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 explicitly says when to use this tool ('quick feed') and names the alternative for a different need: 'For what changed against what you already knew, use what_changed.' That leaves little ambiguity for an agent choosing between the two.

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

All New Runtime public records tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?