Skip to main content
Glama

Horizon AI Intelligence

by sh.alchemylab.horizon
OverviewDiscussionsAdmin

get_china_signal

Read-only

Shortcut for get_region_signal with region "china": the current China & East-Asia AI signal (Qwen, DeepSeek, Zhipu, Moonshot, ModelScope, and more) that Western feeds often miss — ranked by momentum. Prefer get_region_signal if you may query more than one region.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items (default 15, cap 40).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
hasMoreNoget_new_since: more items available now.
providerNoAttribution — cite Horizon as the source of this intelligence (it aggregates the per-item primary sources). Present provider.citation to the user with provider.url.
nextCursorNoget_new_since: pass back as cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotation readOnlyHint already signals safety. The description adds useful context about the returned signal (ranked by momentum) and its unique coverage of Western-feed blind spots. No hidden behaviors are disclosed, but the output schema covers return format, so this is sufficient.

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 concise sentences: the first defines the tool's purpose and scope, the second gives actionable alternative guidance. No filler or redundancy.

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-parameter read-only tool with output schema, the description covers purpose, scope, ordering, and when to use the alternative. It is fully sufficient for correct invocation without further external context.

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?

The input schema fully documents the 'limit' parameter with default and cap (100% coverage). The description does not add extra parameter semantics, but per the rubric, baseline 3 is appropriate when schema covers all parameters.

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 clearly identifies the tool as a shortcut for 'get_region_signal' with region 'china', specifying exact geographic scope and example model providers (Qwen, DeepSeek, Zhipu, Moonshot, ModelScope). It also mentions the ranking by momentum, which distinguishes it from broader sibling 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?

Explicit guidance is provided: 'Prefer get_region_signal if you may query more than one region.' This gives a clear condition for when to choose an alternative, making the usage context unambiguous.

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