New Runtime public records

Read the latest weekly metadox

get_latest_metadox

Read-onlyIdempotent

Use when you want one synthesis of the week in AI engineering instead of a list: the newest weekly metadox (the week's central contradiction, counter-evidence and dated forecasts) as Markdown, up to 12,000 characters, with title, date and URL. Free, no auth. No arguments.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	No	newruntime.com page.
`date`	No	Metadox date.
`json`	No	Machine-readable twin.
`slug`	No	Metadox slug.
`title`	No	Metadox title.
`earlier`	No	Up to three earlier metadoxes.
`markdown`	No	Markdown body (capped), or null.
`next_due`	No	When available is false: the next scheduled metadox.
`schedule`	No	When available is false: the publication schedule.
`available`	Yes	False before the first metadox; then next_due and alternatives are given instead.
`truncated`	No	True when the Markdown was cut at the cap.
`alternatives`	No	When available is false: tools to use meanwhile.
`markdown_url`	No	Markdown route.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "alternatives": {
+      "description": "When available is false: tools to use meanwhile.",
+      "type": "string"
+    },
+    "available": {
+      "description": "False before the first metadox; then next_due and alternatives are given instead.",
+      "type": "boolean"
+    },
+    "date": {
+      "description": "Metadox date.",
+      "type": "string"
+    },
+    "earlier": {
+      "description": "Up to three earlier metadoxes.",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Record date, YYYY-MM-DD."
+          },
+          "json": {
+            "description": "Machine-readable twin of the page."
+          },
+          "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"
+    },
+    "json": {
+      "description": "Machine-readable twin.",
+      "type": "string"
+    },
+    "markdown": {
+      "description": "Markdown body (capped), or null."
+    },
+    "markdown_url": {
+      "description": "Markdown route.",
+      "type": "string"
+    },
+    "next_due": {
+      "description": "When available is false: the next scheduled metadox."
+    },
+    "schedule": {
+      "description": "When available is false: the publication schedule.",
+      "type": "string"
+    },
+    "slug": {
+      "description": "Metadox slug.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Metadox title.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when the Markdown was cut at the cap.",
+      "type": "boolean"
+    },
+    "url": {
+      "description": "newruntime.com page.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "available"
+  ],
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The description adds significant behavioral context beyond the annotations by stating it is 'Free, no auth' and defining the output constraints (up to 12,000 characters, title, date, URL). This operational context is crucial for an AI agent planning its execution environment.

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 highly efficient, using one dense paragraph to convey the 'what,' 'why,' 'how much,' and 'cost/authentication' of the tool without any wasted words.

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 that the tool accepts zero arguments, this definition is maximally complete. It specifies the exact content, format, and limitations of the resulting data, eliminating ambiguity for the invoking agent.

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?

Since the input schema has zero parameters, the description is fully responsible for defining the tool's scope and function. The baseline score of 4 applies as the description handles the entire operational definition.

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 clearly states the function: providing a synthesis of the week in AI engineering. It specifies exactly what this 'metadox' contains (contradictions, forecasts) and its format (Markdown), making it immediately clear what the tool delivers.

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?

The tool explicitly tells the agent when to use it—'Use when you want one synthesis... instead of a list.' This guides the AI perfectly towards choosing this tool for high-level over lower-level retrieval tasks found in siblings like 'search_archive'.

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?