Skip to main content
Glama
Sign In

Horizon: AI News & AI Regulation Tracker

by sh.alchemylab.horizon
OverviewDiscussionsAdmin

get_daily_briefing

Read-only

Today's AI briefing, or any past day's: top stories with their sources and corroboration labels, emerging signals, new entrants, and regulation updates. Drawn from Hacker News, Reddit, Bluesky, arXiv, Hugging Face, lab blogs, tech press in the US, Europe and East Asia, and legislative sources. A curated once-daily synthesis — for raw item-level updates since your last check, use get_new_since instead. Pass a date (YYYY-MM-DD) for a past day; set top_stories_only for a shorter result.

Input Schema

NameRequiredDescriptionDefault
dateNoOptional YYYY-MM-DD for a past briefing (any date in the archive); omit for the latest briefing.
top_stories_onlyNoOptional. True returns only the top stories with their sources, leaving out signals, new entrants, movers, regional highlights and regulation. Omit for the whole briefing.

Output Schema

NameRequiredDescriptionDefault
briefingYes
providerYesAttribution: Horizon aggregated this result, and each item also names its own primary source. citation credits both; url is the Horizon page for this result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / top_stories_only
      Added value: +{
+  "description": "Optional. True returns only the top stories with their sources, leaving out signals, new entrants, movers, regional highlights and regulation. Omit for the whole briefing.",
+  "type": "boolean"
+}
    • 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
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "briefing": {
+      "properties": {
+        "content": {
+          "description": "topStories, emergingSignals, newEntrants, regulation, ...",
+          "type": "object"
+        },
+        "date": {
+          "type": "string"
+        },
+        "generatedAt": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "date",
+        "content"
+      ],
+      "type": "object"
+    },
+    "provider": {
+      "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"
+    }
+  },
+  "required": [
+    "briefing",
+    "provider"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional YYYY-MM-DD within the last 7 days; omit for the latest briefing."New value: +"Optional YYYY-MM-DD for a past briefing (any date in the archive); omit for the latest briefing."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real context beyond that: the source corpus (HN, Reddit, Bluesky, arXiv, HF, lab blogs, tech press across three regions, legislative sources) and the once-daily curated cadence. It stops short of stating archive bounds, freshness timing, or result size, which is why it is a 4 rather than a 5.

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?

The core purpose is front-loaded in the first clause, and the routing hint comes before the parameter notes. The source enumeration is long but earns its place by establishing coverage trust; four sentences are close to the minimum for this much content, though the source list could be tightened slightly.

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?

With an output schema present, the return shape need not be described, and the description still characterizes what categories of content come back. Parameters are covered, the sibling alternative is named, and the curated-daily model versus incremental updates is made clear — nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100%, so both parameters are already fully documented in the schema, making 3 the baseline. The description restates the date format and adds only a marginal nuance ('a shorter result' for top_stories_only) rather than new semantics such as behavior for out-of-range dates or what 'latest' means.

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?

The description opens with a specific verb+resource ('Today's AI briefing, or any past day's') and enumerates the concrete contents: top stories with sources and corroboration labels, emerging signals, new entrants, regulation updates. It also explicitly contrasts itself with the sibling get_new_since, so an agent can distinguish the two 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 Guidelines5/5

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

It gives an explicit alternative and the condition that selects it: 'for raw item-level updates since your last check, use get_new_since instead.' It also states the selection conditions for both parameters (pass a date for a past day, set top_stories_only for a shorter result).

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