Ai Briefing

Get Recent

get_recent

Read-onlyIdempotent

Retrieve AI developments from the last N days (default 7), filterable by category (e.g., model_release, paper, mcp), source (e.g., arxiv, github), and importance (low/normal/high/breaking). The category is a keyword label derived from the headline at ingest, not a curated classification — filtering by it narrows the feed but does not guarantee every row belongs; the response repeats this caveat whenever a category filter is applied.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Look back N days (default 7)
`limit`	No	Max results (default 20)
`source`	No	Filter by source (e.g., arxiv, hackernews, github)
`category`	No	Filter by category (e.g., model_release, paper, funding). Heuristic headline label, not a curated taxonomy — check the titles.
`importance`	No	Filter by importance: low, normal, high, breaking

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	Number of developments found
`period`	Yes	Time period description
`developments`	Yes	Recent developments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / category / description

Previous value: -"Filter by category (e.g., model_release, paper, funding)"New value: +"Filter by category (e.g., model_release, paper, funding). Heuristic headline label, not a curated taxonomy — check the titles."

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "category": "mcp",
+    "days": 7
+  },
+  {
+    "importance": "high",
+    "limit": 10,
+    "source": "github"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "developments": {
+      "description": "Recent developments",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Development category",
+            "type": "string"
+          },
+          "importance": {
+            "description": "Importance level",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "Publication timestamp",
+            "type": "string"
+          },
+          "source": {
+            "description": "Source identifier",
+            "type": "string"
+          },
+          "summary": {
+            "description": "Development summary",
+            "type": "string"
+          },
+          "title": {
+            "description": "Development title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Source URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "period": {
+      "description": "Time period description",
+      "type": "string"
+    },
+    "total": {
+      "description": "Number of developments found",
+      "type": "number"
+    }
+  },
+  "required": [
+    "period",
+    "total",
+    "developments"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "limit": 10,
-    "minmagnitude": 4.5
-  },
-  {
-    "minmagnitude": 2.5
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Total number of earthquakes in response",
-      "type": "number"
-    },
-    "earthquakes": {
-      "description": "List of recent earthquakes",
-      "items": {
-        "properties": {
-          "alert": {
-            "description": "Alert level if applicable",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "depth_km": {
-            "description": "Depth below surface in kilometers",
-            "type": "number"
-          },
-          "id": {
-            "description": "USGS event ID",
-            "type": "string"
-          },
-          "latitude": {
-            "description": "Epicenter latitude",
-            "type": "number"
-          },
-          "longitude": {
-            "description": "Epicenter longitude",
-            "type": "number"
-          },
-          "magnitude": {
-            "description": "Earthquake magnitude",
-            "type": "number"
-          },
-          "place": {
-            "description": "Location description",
-            "type": "string"
-          },
-          "significance": {
-            "description": "Event significance score",
-            "type": "number"
-          },
-          "time": {
-            "description": "Event time in ISO 8601 format",
-            "type": "string"
-          },
-          "tsunami": {
-            "description": "Tsunami warning flag",
-            "type": "boolean"
-          },
-          "type": {
-            "description": "Event type (e.g., earthquake)",
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "magnitude",
-          "place",
-          "time",
-          "latitude",
-          "longitude",
-          "depth_km",
-          "type",
-          "tsunami",
-          "significance"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "earthquakes"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of earthquakes in response",
+      "type": "number"
+    },
+    "earthquakes": {
+      "description": "List of recent earthquakes",
+      "items": {
+        "properties": {
+          "alert": {
+            "description": "Alert level if applicable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "depth_km": {
+            "description": "Depth below surface in kilometers",
+            "type": "number"
+          },
+          "id": {
+            "description": "USGS event ID",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Epicenter latitude",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Epicenter longitude",
+            "type": "number"
+          },
+          "magnitude": {
+            "description": "Earthquake magnitude",
+            "type": "number"
+          },
+          "place": {
+            "description": "Location description",
+            "type": "string"
+          },
+          "significance": {
+            "description": "Event significance score",
+            "type": "number"
+          },
+          "time": {
+            "description": "Event time in ISO 8601 format",
+            "type": "string"
+          },
+          "tsunami": {
+            "description": "Tsunami warning flag",
+            "type": "boolean"
+          },
+          "type": {
+            "description": "Event type (e.g., earthquake)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "magnitude",
+          "place",
+          "time",
+          "latitude",
+          "longitude",
+          "depth_km",
+          "type",
+          "tsunami",
+          "significance"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "earthquakes"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10,
+    "minmagnitude": 4.5
+  },
+  {
+    "minmagnitude": 2.5
+  }
+]

First observedApr 22, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already declare this read-only, idempotent, and non-destructive, and the description adds genuinely useful behavior beyond those flags: the category filter is a heuristic headline-derived label rather than a curated taxonomy, and the response repeats that caveat whenever the filter is applied. This manages agent expectations about result reliability without contradicting the annotations.

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 carry the entire definition: the first front-loads the action, time window, and filters; the second isolates the important caveat. The first sentence is somewhat long with embedded examples, but nothing is wasted and the caveat is cleanly separated.

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?

For a simple read-only feed tool, the description covers the time window, all filter dimensions, defaults, and the key reliability caveat, and the presence of an output schema means return values need no explanation. It lacks explicit sibling differentiation, which is covered more under usage guidelines, but the definition is otherwise complete enough for correct invocation.

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?

With 100% schema description coverage, the baseline is 3 because the schema already documents each parameter. The description adds value by explaining that category is an ingest-time heuristic label, not a curated classification, and by giving concrete example values for category, source, and importance. It mostly restates defaults already in the schema, so it does not earn a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and object ('Retrieve AI developments') and bounds the scope to a time window ('last N days, default 7') plus three filter dimensions. It makes the tool's role clear, though it never names or contrasts sibling tools such as search_developments or get_ai_news, so differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given for when to choose this tool over alternatives; there are no 'use this when' or 'for X use Y instead' statements. The filter and caveat content describe mechanics, not selection criteria, so an agent must infer when get_recent is the right call among several similar-looking feed/search tools.

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

All Ai Briefing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Get Recent

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources