get_trendingWhat's surging in global news right now: topics whose coverage is ≥2 standard deviations above their trailing average (z-score), the biggest week-over-week movers, and surging countries. Derived every 2 hours from GDELT across 65+ languages.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| meta | No | ||
| movers | No | ||
| surging | No | ||
| surgingCountries | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "meta": {
+ "properties": {
+ "attribution": {
+ "type": "string"
+ },
+ "license": {
+ "type": "string"
+ },
+ "source": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "movers": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "latestVolIntensity": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "meta": {
+ "properties": {
+ "attribution": {
+ "type": "string"
+ },
+ "license": {
+ "type": "string"
+ },
+ "source": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "wowChange": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "surging": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "latestVolIntensity": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "meta": {
+ "properties": {
+ "attribution": {
+ "type": "string"
+ },
+ "license": {
+ "type": "string"
+ },
+ "source": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "zScore": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "surgingCountries": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "iso2": {
+ "type": "string"
+ },
+ "meta": {
+ "properties": {
+ "attribution": {
+ "type": "string"
+ },
+ "license": {
+ "type": "string"
+ },
+ "source": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "name": {
+ "type": "string"
+ },
+ "zScore": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds behavioral context beyond annotations: derived every 2 hours from GDELT across 65+ languages. No contradiction with readOnlyHint annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first defines purpose and metrics, second adds frequency and source. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with output schema, description fully explains what is returned and update frequency. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters, so baseline 4 applies. Description adds value by explaining output metrics (z-score, movers, surging countries), though not required for this dimension.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly defines verb ('surging'), resource ('global news topics'), and specific metrics (z-score, week-over-week movers, surging countries). Distinguishes from siblings by focusing on trending/surging data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies usage context (trending vs other tools) and states update frequency ('every 2 hours'), but does not explicitly state when not to use or name alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.