Geotone — Global News Signals

Topic statistics

get_topic

Read-only

Live media-coverage statistics for one geopolitical topic (e.g. 'ukraine-war', 'taiwan-strait', 'sanctions'): 90-day daily volume and tone series, z-score, week-over-week change, and a sample of recent articles (headline+link only). Use search_topics to find slugs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Topic slug, e.g. 'ukraine-war'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`name`	Yes
`page`	No
`slug`	Yes
`stats`	No
`articles`	No
`snapshots`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "articles": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "meta": {
+            "properties": {
+              "attribution": {
+                "type": "string"
+              },
+              "license": {
+                "type": "string"
+              },
+              "source": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "properties": {
+        "attribution": {
+          "type": "string"
+        },
+        "license": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "page": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "snapshots": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "meta": {
+            "properties": {
+              "attribution": {
+                "type": "string"
+              },
+              "license": {
+                "type": "string"
+              },
+              "source": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "toneAvg": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "volIntensity": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "volRaw": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "stats": {
+      "additionalProperties": true,
+      "properties": {
+        "meta": {
+          "properties": {
+            "attribution": {
+              "type": "string"
+            },
+            "license": {
+              "type": "string"
+            },
+            "source": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "wowChangePct": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "zScore": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "snapshots"
+  ],
+  "type": "object"
+}

First observedJul 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description details the data scope (90-day series, z-score, week-over-week change, article headlines/links) and notes what is not included (full text). This adds meaningful insight into the tool's behavior and limitations.

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, no wasted words. Core purpose is front-loaded in the first sentence; the second provides actionable guidance. Efficient and clear.

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 one-parameter tool with an output schema, the description covers all essential aspects: what it returns (specific metrics), time range, and how to get input. No gaps given the complexity.

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% with a clear description of the 'slug' parameter. The description adds extra value by advising to use search_topics to obtain the slug, which is not in the schema, enhancing parameter understanding.

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 it provides live media-coverage statistics for a geopolitical topic, listing specific outputs (volume, tone, z-score, change, article samples). It distinguishes from siblings by focusing on media-coverage stats vs. other get_* tools which likely cover different scopes.

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 mentions using search_topics to find slugs, guiding the agent on a necessary prerequisite. However, it does not explicitly address when to prefer this over sibling tools like get_briefing or get_trending, leaving room for improvement.

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?