Skip to main content
Glama
Sign In

Horizon: AI News & AI Regulation Tracker

by sh.alchemylab.horizon
OverviewDiscussionsAdmin

get_related

Read-only

Semantic 'more like this': given an item id (from get_new_since, search_news, or the feed), returns the most similar recent items by embedding similarity. Titles, sources, similarity scores, links.

Input Schema

NameRequiredDescriptionDefault
idYesUUID of an item from a previous result.
limitNoMax related items (default 10, cap 25).

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds useful behavioral context beyond annotations: similarity is embedding-based, results are recent, and output includes titles, sources, scores, and links. It does not describe rate limits or auth, but those are not necessary here.

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 no wasted text. The core 'more like this' purpose is front-loaded, followed by the id provenance and return shape.

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 simple read-only related-items tool with rich annotations, fully documented parameters, and an output schema, the description provides enough context to invoke it correctly. No critical behavior or parameter information 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 coverage is 100%, so the schema already defines both parameters. The description adds some useful provenance for the id parameter by naming tools that produce valid ids, but it does not add limit semantics beyond what the schema documents. A 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?

The description states a specific verb-like operation ('Semantic more like this') and resource ('most similar recent items'), and it distinguishes the tool from search/get-new workflows by explaining that it takes an item id and returns embedding-similar results. An agent can identify its role without opening the 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?

It clearly indicates the usage context: the caller should already have an item id from get_new_since, search_news, or the feed. It does not explicitly state when not to use it or name an alternative for broad search, but the intended workflow is clear.

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