Horizon: AI News & AI Regulation Tracker

get_topic_signal

Read-only

The current AI signal for a topic — recent, relevance-scored items tagged with that topic, ranked by momentum. Like get_region_signal but sliced by subject instead of geography.

Input Schema

Name	Required	Description	Default
`limit`	No	Max items (default 15, cap 40).
`topic`	Yes	Topic slug.

Output Schema

Name	Required	Description
`items`	Yes
`hasMore`	No	get_new_since: more items available now.
`provider`	No	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.
`nextCursor`	No	get_new_since: pass back as cursor.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

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

Changed1 schema field changedJul 20, 2026

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

AddedJul 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered. The description adds non-obvious behavior beyond them: items are recent, relevance-scored, and ranked by momentum — telling the agent the output ordering is momentum-based, not chronological.

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 tight sentences with the purpose front-loaded and the sibling comparison second. No filler or redundancy.

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?

An output schema exists, so return-value detail is not required, and the description conveys the semantic shape (ranked, relevance-scored items). Minor gap: nothing about how momentum is computed or whether results are paginated, but that's beyond the stated contract.

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%: the enum slugs and the limit default/cap (15/40) are fully documented in the schema. The description adds no parameter-level detail (e.g., what 'momentum' means for ranking or how limit interacts with ranking), so baseline 3 is appropriate.

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 ('get') and resource ('current AI signal for a topic') plus the content type (recent, relevance-scored items tagged with that topic). The contrast with get_region_signal makes the distinction from the nearest sibling explicit.

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?

'Like get_region_signal but sliced by subject instead of geography' routes the agent to the right sibling by contrast, which is strong usage guidance. It stops short of an explicit when-not condition or prerequisite, so it isn't a full 5.

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 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?