Skip to main content
Glama
Sign In

New Runtime public records

by com.newruntime
OverviewDiscussionsAdmin

Brief on one New Runtime topic

get_topic_brief
Read-onlyIdempotent

Use when you need the background on one AI-engineering topic in one call: its summary, what was published on it in the last fortnight, and the top related patterns, shifts, field notes and news signals with URLs. Free, no auth. Example: {"topic": "coding-agents"}. Topic list: https://newruntime.com/topics.json.

Input Schema

NameRequiredDescriptionDefault
topicYesTopic slug or name.

Output Schema

NameRequiredDescriptionDefault
labelNoTopic label.
topicYesTopic slug.
answerNoShort answer: the current state of the topic.
countsNoRecord counts per collection.
routesNoHTML, Markdown and JSON routes of the topic page.
shiftsNoShifts on the topic.
patternsNoPatterns on the topic.
descriptionNoTopic description.
field_notesNoField Notes on the topic.
latest_liveNoLatest records in the topic's live window.
raw_signalsNoRaw Signals on the topic.
top_sourcesNoMost cited source hosts.
last_updatedNoLast update of the topic.
atlas_recordsNoAtlas records on the topic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "answer": {
+      "description": "Short answer: the current state of the topic.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "atlas_records": {
+      "description": "Atlas records on the topic.",
+      "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"
+    },
+    "counts": {
+      "description": "Record counts per collection.",
+      "properties": {},
+      "type": "object"
+    },
+    "description": {
+      "description": "Topic description."
+    },
+    "field_notes": {
+      "description": "Field Notes on the topic.",
+      "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"
+    },
+    "label": {
+      "description": "Topic label.",
+      "type": "string"
+    },
+    "last_updated": {
+      "description": "Last update of the topic."
+    },
+    "latest_live": {
+      "description": "Latest records in the topic's live window.",
+      "properties": {},
+      "type": "object"
+    },
+    "patterns": {
+      "description": "Patterns on the topic.",
+      "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"
+    },
+    "raw_signals": {
+      "description": "Raw Signals on the topic.",
+      "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"
+    },
+    "routes": {
+      "description": "HTML, Markdown and JSON routes of the topic page.",
+      "properties": {},
+      "type": "object"
+    },
+    "shifts": {
+      "description": "Shifts on the topic.",
+      "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"
+    },
+    "top_sources": {
+      "description": "Most cited source hosts.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "topic": {
+      "description": "Topic slug.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "topic"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / topic / examples
      Added value: +[
+  "agents",
+  "coding-agents",
+  "mcp"
+]
  3. Added

TDQS

A4.3/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, closed-world, so the description correctly avoids restating safety. It instead adds genuinely new operational context: 'Free, no auth' (auth requirement an agent must otherwise discover) and a data-recency window ('last fortnight') that constrains result freshness.

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?

Two sentences, front-loaded with the 'Use when' trigger, then payload contents, then the practical example and lookup URL. Dense but every clause carries information; only the redundant example object slightly duplicates the schema's examples field.

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?

With an output schema present, the description needn't document return shape, and with a single fully-described parameter plus annotations, the main gaps are closed. Nearly complete — it could mention an error case for an invalid slug, since the topic list URL implies failures are possible, but nothing critical is missing.

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 baseline is 3. The description goes beyond the schema by supplying the topic-list URL (https://newruntime.com/topics.json), which tells the agent how to resolve a valid slug — the schema only offers three examples and says 'slug or name'. The inline example call is marginal since examples already exist in the schema.

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+resource ('get a brief on one AI-engineering topic') and enumerates exactly what the brief contains: summary, last-fortnight publications, related patterns/shifts/field notes/news signals with URLs. This is concrete enough to distinguish it from list/search siblings like search_archive or whats_new without opening either 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?

The opening 'Use when you need the background on one AI-engineering topic in one call' gives a clear activation context, reinforced by the 'one call' framing that implicitly argues against assembling the same data from search/archive tools. It does not explicitly name an alternative or state when-not to use it, so it stops short of a 5.

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 toolsInspect
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