Horizon AI Intelligence

get_regulation_updates

Read-only

Current AI legislation headlines across the US Congress and federal agencies, US state legislatures, the UK Parliament, and the EU, with each item's legislative stage (proposed / committee / floor action / passed / implementation). State bills are the largest share by far; filter with jurisdiction to narrow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max headlines (default 50, cap 100).
`jurisdiction`	No	Optional filter to one jurisdiction.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	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.

Changed2 schema fields changedSep 14, 2026

changedInput schema / properties / jurisdiction / enum

Previous value: -[
-  "us_federal",
-  "uk",
-  "eu"
-]New value: +[
+  "us_federal",
+  "us_state",
+  "uk",
+  "eu"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "jurisdiction": {
+            "description": "us_federal | us_state | uk | eu",
+            "type": "string"
+          },
+          "lastUpdated": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sourceUrl": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stage": {
+            "description": "Legislative stage as recorded from the source.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "jurisdiction"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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": [
+    "items",
+    "provider"
+  ],
+  "type": "object"
+}

First observedJul 5, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful context about the state-bill majority and legislative-stage breakdown, but does not disclose freshness, pagination, or rate-limit behavior. This is adequate but not rich.

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 main scope is front-loaded, followed by the key usage hint about state bills and jurisdiction filtering. Every clause 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?

With an output schema, no required parameters, and annotations declaring read-only behavior, the description provides all necessary context to call the tool correctly. Jurisdiction options and limit semantics are already in the schema, so nothing essential 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 documented. The description adds a helpful hint that state bills dominate and that jurisdiction narrows results, but this mostly reinforces the schema rather than adding new meaning.

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: get current AI legislation headlines. It enumerates the jurisdictions (US Congress/federal agencies, US states, UK Parliament, EU) and names the included legislative stages, making it easy to distinguish from sibling news/signal tools.

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?

The description gives clear context on what the tool returns and explicitly suggests using the jurisdiction filter to narrow state-heavy results. It does not name alternative tools or exclusions, but the context is enough to infer when this tool applies.

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?