Skip to main content
Glama

Ai Briefing

by io.github.pipeworx-io

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook back N days (default 7)
limitNoMax results (default 20)
sourceNoFilter by source (e.g., arxiv, hackernews, github)
categoryNoFilter by category (e.g., model_release, paper, funding)
importanceNoFilter by importance: low, normal, high, breaking

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesNumber of developments found
periodYesTime period description
developmentsYesRecent developments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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"
+}
  2. Changed2 schema fields changed
    • 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
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "minmagnitude": 4.5
+  },
+  {
+    "minmagnitude": 2.5
+  }
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. Description adds filtering capabilities and default days, but does not disclose potential caveats like data freshness limits, pagination, or rate limits. Adds moderate value beyond annotations.

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?

Single sentence is extremely concise, front-loaded with the core action and scope, and contains no redundant or unnecessary words. Every element serves a purpose.

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?

Description covers key features (time range, filters, defaults) and is supported by a complete output schema. Slightly lacks detail on default ordering or pagination behavior, but overall sufficient for a filtered retrieval tool.

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 coverage is 100% with clear descriptions and examples for all 5 parameters. Description mentions days, category, source, and importance but adds no new semantic detail beyond what the schema provides. Baseline of 3 is appropriate.

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?

Description clearly states verb 'Retrieve', resource 'AI developments', and temporal scope 'last N days' with filtering options. Distinguishes from siblings like 'deep_research' and 'get_ai_news' by focusing on recency and structured filtering, but lacks explicit differentiation.

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

Usage Guidelines3/5

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

Implied usage for retrieving recent AI developments, but no explicit guidance on when to use this tool versus alternatives (e.g., 'get_ai_news', 'search_developments'). No exclusions or when-not scenarios provided.

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

All Ai Briefing toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as multiple tools for querying Pipeworx data (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) and numerous tools for AI news/tools (get_ai_news, get_ai_toolbelt, get_briefing, get_model_landscape, etc.). This will cause an agent to frequently misselect the appropriate tool.

Naming Consistency4/5

Most tools follow a verb_noun pattern in snake_case (e.g., compare_entities, discover_tools, get_briefing). However, a few deviate like 'bet_research' (noun_verb) and 'what_happened' (phrase), but overall the pattern is largely consistent.

Tool Count2/5

38 tools is excessive for a server called 'Ai Briefing', which suggests a focused purpose. The tool count spans multiple domains (AI visibility, Pipeworx queries, Polymarket betting, memory, subscriptions) making it feel overstuffed and unfocused.

Completeness3/5

The tool set covers many aspects of its broad domain (querying, comparing, subscribing, memory), but there are notable gaps: no tool for modifying subscriptions, no user profile management, and the AI news tools overlap rather than cover distinct needs.

Resources