Horizon AI Intelligence

get_daily_briefing

Read-only

Today's aggregate AI industry briefing: top stories, emerging signals, new entrants, and regulation updates, distilled from HN/Reddit and official legislative sources. A curated once-daily synthesis — for raw item-level updates since your last check, use get_new_since instead. Optionally pass any past date (YYYY-MM-DD) — the full briefing archive is public.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Optional YYYY-MM-DD for a past briefing (any date in the archive); omit for the latest briefing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`briefing`	Yes
`provider`	Yes	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

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"
+}

Changed1 schema field changedJul 15, 2026

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

First observedJul 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral context: the briefing is curated, once-daily, synthesized from HN/Reddit and legislative sources, and the full archive is public. No contradictions with 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?

Two sentences with no filler: the first front-loads what the tool returns and its sources, and the second handles the alternative tool and date behavior. Every sentence earns its place.

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 single optional-parameter read-only tool with an output schema, the description covers purpose, sources, behavior, date handling, and the key alternative. Nothing essential is missing for an agent to select and invoke it correctly.

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 the schema fully documents the optional date parameter. The description restates the date format and archive availability, but adds little beyond what the schema already provides.

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 and resource ('aggregate AI industry briefing') and lists the content categories: top stories, emerging signals, new entrants, and regulation updates. It also names the sibling it is not (get_new_since), so an agent can distinguish it from raw item-level tools.

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?

Explicitly says to use get_new_since instead when raw item-level updates since the last check are needed, making the boundary between the two tools clear. It also explains that any past date can be passed and that omitting it returns the latest briefing.

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

All Horizon AI Intelligence 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.

Resources

Need Help?