Geotone — Global News Signals

Story timeline

get_story_chain

Read-only

A story timeline: the threaded developments of one multi-day event chain, oldest first (e.g. attack → casualties confirmed → international reaction). Use the chain_id values returned by get_wire. Each development is a headline + link + outlet count + tone.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain_id`	Yes	Chain id from get_wire

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`meta`	No
`page`	No
`country`	No
`firstSeen`	No
`developments`	Yes
`lastDevelopment`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "country": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "developments": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "domain": {
+            "type": "string"
+          },
+          "firstSeen": {
+            "type": "string"
+          },
+          "meta": {
+            "properties": {
+              "attribution": {
+                "type": "string"
+              },
+              "license": {
+                "type": "string"
+              },
+              "source": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "outlets": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "toneAvg": {
+            "type": "number"
+          },
+          "topic": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "firstSeen": {
+      "type": "string"
+    },
+    "id": {
+      "type": "number"
+    },
+    "lastDevelopment": {
+      "type": "string"
+    },
+    "meta": {
+      "properties": {
+        "attribution": {
+          "type": "string"
+        },
+        "license": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "page": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "developments"
+  ],
+  "type": "object"
+}

First observedJul 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already signal read-only behavior. Description adds value by revealing chronological ordering (oldest first) and the structure of developments, which are not in 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?

Three concise sentences front-load the core purpose and example, with no wasted words. Every sentence adds necessary information.

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?

Sufficient for a simple read tool with one parameter and an output schema. Could mention limits or pagination, but the given details cover essential usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning by explaining the chain_id parameter's origin (from get_wire) and its role in retrieving a specific story chain.

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 states the tool provides 'threaded developments of one multi-day event chain' with oldest first ordering and example structure. It includes specific components (headline, link, outlet count, tone) and distinguishes from siblings by referencing get_wire and chain_id.

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?

Explicitly instructs to use chain_id from get_wire, providing clear context for when to invoke. However, lacks comparisons with siblings or when-not-to-use guidance.

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

All Geotone — Global News Signals tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?