New Runtime public records

Search the New Runtime archive

search_archive

Read-onlyIdempotent

Use when you need dated, source-linked coverage of an AI-engineering product, company or topic (agents, MCP, coding tools, model releases) without crawling the web. Searches New Runtime's Field Notes, Raw Signals and Analyses; returns up to 10 hits with title, date, one-line summary and URL. Free, no auth. Example: {"query": "MCP security", "limit": 5}. Then get_record for the full text.

Input Schema

Name	Required	Description	Default
`kind`	No	signal = source-linked news item, post = Field Note, analysis = long-form analysis.	any
`limit`	No
`query`	Yes	Words to look for (product, company, topic).

Output Schema

Name	Required	Description	Default
`query`	Yes	The query as searched.
`results`	Yes	Up to `limit` hits, best first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "The query as searched.",
+      "type": "string"
+    },
+    "results": {
+      "description": "Up to `limit` hits, best first.",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Record date."
+          },
+          "description": {
+            "description": "One-line summary."
+          },
+          "kind": {
+            "description": "post | signal | analysis."
+          },
+          "slug": {
+            "description": "Record slug."
+          },
+          "title": {
+            "description": "Record title."
+          },
+          "url": {
+            "description": "newruntime.com page; pass it to get_record."
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "results"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / kind / description

Added value: +"signal = source-linked news item, post = Field Note, analysis = long-form analysis."

addedInput schema / properties / query / examples

Added value: +[
+  "MCP security",
+  "Claude Code plugins",
+  "agent memory"
+]

AddedSep 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, which already establish read-only, idempotent, non-destructive, non-open-world behavior, the description adds cost and auth context ('Free, no auth'), result volume ('up to 10 hits'), returned fields, and the next-step retrieval path via get_record.

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 front-loaded with the use condition, then concisely covers sources, return shape, auth/cost, an example, and the follow-up tool. Every sentence earns its place with no filler.

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 the existing output schema and annotations, the description provides everything needed to call the tool correctly: when to use it, what it searches, what it returns, cost/auth, an example, and how to get full text afterward.

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 description coverage is 67%, so the schema already documents the query, kind enum, and limit constraints. The description adds an example call and clarifies that results are capped at 10, but it does not meaningfully explain the kind parameter or add syntax beyond what the schema provides.

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: searching New Runtime's Field Notes, Raw Signals and Analyses for dated, source-linked AI-engineering coverage. It distinguishes itself from the sibling get_record by explicitly positioning itself as the search step before full-text retrieval.

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?

It gives a clear use condition ('Use when you need dated, source-linked coverage ... without crawling the web') and names the follow-up tool get_record for full text. It does not explicitly state when not to use it versus sibling tools like get_topic_brief or what_changed, so it falls short of full when/when-not guidance.

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?