Skip to main content
Glama
Sign In

Horizon: AI News & AI Regulation Tracker

by sh.alchemylab.horizon
OverviewDiscussionsAdmin

search_news

Read-only

Quick title search over the last 14 days of AI news: returns the top 3 matches by momentum, with links and item ids (pass one to get_related).

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms.

Output Schema

NameRequiredDescriptionDefault
itemsYes
hasMoreNoget_new_since: more items available now.
providerNoAttribution: Horizon aggregated this result, and each item also names its own primary source. citation credits both; url is the Horizon page for this result.
nextCursorNoget_new_since: pass back as cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / provider / description
      Previous value: -"Attribution — cite Horizon as the source of this intelligence (it aggregates the per-item primary sources). Present provider.citation to the user with provider.url."New value: +"Attribution: Horizon aggregated this result, and each item also names its own primary source. citation credits both; url is the Horizon page for this result."
  2. Changed1 schema field changed
    • addedOutput schema / properties / provider
      Added value: +{
+  "description": "Attribution — cite Horizon as the source of this intelligence (it aggregates the per-item primary sources). Present provider.citation to the user with provider.url.",
+  "properties": {
+    "citation": {
+      "description": "Ready-to-paste citation string.",
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "url": {
+      "description": "Canonical Horizon page for this result.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "hasMore": {
+      "description": "get_new_since: more items available now.",
+      "type": "boolean"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Item UUID — pass to get_related.",
+            "type": "string"
+          },
+          "publishedAt": {
+            "description": "ISO 8601 timestamp.",
+            "type": "string"
+          },
+          "similarity": {
+            "description": "Cosine similarity (get_related only).",
+            "type": "number"
+          },
+          "source": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topics": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "title",
+          "source",
+          "publishedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "description": "get_new_since: pass back as cursor.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world behavior and an output schema exists, yet the description still adds non-obvious traits: a hard cap of 3 results, ranking by momentum, a 14-day window, and that ids are consumable by get_related. Missing only rate-limit or empty-result behavior.

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?

A single sentence that front-loads the core capability and packs scope, result cap, ranking, and follow-up in the tail. 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?

For a one-parameter read tool with annotations and an output schema, the description covers purpose, scope, result size, and the downstream id pattern; nothing an agent needs to invoke it correctly is absent.

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 a single fully documented parameter, the schema baseline is high, but the description adds real meaning beyond 'Search terms' by specifying that matching is against titles only and is time-bounded. No format/syntax guidance for multi-term queries.

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 concrete verb+resource ('title search over AI news') plus scope (last 14 days) and behavior (top 3 by momentum, links and item ids). An agent can distinguish it from siblings like get_topic_signal or get_new_since without opening any 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?

Frames it as a 'quick title search' with a bounded window, which signals it is the lightweight lookup rather than a broad retrieval, and it explicitly hands off ids to get_related. It does not say when to prefer get_topic_signal, get_china_signal, or get_new_since instead, so routing is only partly covered.

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

All Horizon: AI News & AI Regulation Tracker toolsInspect
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.

Resources