New Runtime public records

Read one New Runtime record

get_record

Read-onlyIdempotent

Use after search_archive, whats_new or what_changed to read one record in full: title, dates, source URLs, topics and body text. Pass the newruntime.com URL you got, or kind + slug. Free, no auth. Example: {"url": "https://newruntime.com/signals//"}.

Input Schema

Name	Required	Description
`url`	No	A https://newruntime.com/posts\|signals\|analysis/<slug>/ URL.
`kind`	No
`slug`	No

Output Schema

Name	Required	Description
`url`	Yes	Canonical newruntime.com URL of the record.
`kind`	Yes	post \| signal \| analysis.
`record`	Yes	The published record: title, dates, source_urls, topics, entities, body and routes.
`truncated`	No	Present and true when body/markdown were dropped to fit the size cap; read the url for the full text.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "kind": {
+      "description": "post | signal | analysis.",
+      "type": "string"
+    },
+    "record": {
+      "description": "The published record: title, dates, source_urls, topics, entities, body and routes.",
+      "properties": {},
+      "type": "object"
+    },
+    "truncated": {
+      "description": "Present and true when body/markdown were dropped to fit the size cap; read the url for the full text.",
+      "type": "boolean"
+    },
+    "url": {
+      "description": "Canonical newruntime.com URL of the record.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "url",
+    "record"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / url / examples

Added value: +[
+  "https://newruntime.com/analysis/claude-plugins-now-depend-on-anthropic-s-distribution-rules/"
+]

AddedSep 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the extra burden is low; the description still adds value with 'Free, no auth', which annotations do not express. It omits what happens when a record is missing, and it doesn't reconcile the fact that the schema marks zero required parameters while the text implies at least one of url or kind+slug is needed.

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?

One dense sentence leads with the precondition and the returned fields, followed by the addressing rule and a literal example. Nothing is redundant and the most decision-relevant clause is first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be spelled out, though the field list is a harmless convenience. The remaining gap is the missing-record path and the ambiguity between zero required parameters in the schema and the 'URL or kind + slug' prerequisite in the prose for a single-record fetch.

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 description coverage is only 33% — url is documented, kind and slug are not — so the description has to compensate, and it does by explaining the two mutually exclusive addressing modes ('pass the URL you got, or kind + slug') with a worked example. It doesn't state that the two modes must not be mixed, nor that no parameter is strictly required, but the calling pattern is clear.

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 specific verb and resource ('read one record in full') and enumerates the payload an agent gets back: title, dates, source URLs, topics and body text. It also positions itself against the sibling search/listing tools (search_archive, whats_new, what_changed), so the agent can tell fetch-one from find-many without opening a schema.

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?

Gives an explicit entry condition — 'use after search_archive, whats_new or what_changed' — which routes the agent from discovery to retrieval. It does not spell out the inverse case (when a caller should stay with the listing tools, or how to fetch many records), but the sequencing guidance is concrete rather than implied.

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?