Skip to main content
Glama

Primary Sources

by io.github.simonmak-ascent
OverviewDiscussionsAdmin

gdelt_news

Read-onlyIdempotent

Search GDELT DOC 2.0 global news (free, no key). Returns matching articles with title, URL, domain, language, seen date and source country, or a volume timeline. Use for news-volume trends and cross-outlet coverage; use hn_search for tech-community discussion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoartlist (articles) or timelinevol (volume)
queryYesGDELT query, e.g. "Hong Kong" or a company name
timespanNoLookback window, e.g. 24h, 7d, 1m
maxrecordsNoMax records, default 20

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesSource payload; fields vary per tool
sourceYesHuman-readable upstream source name
retrievedAtYesISO-8601 timestamp of retrieval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / maxrecords / description
      Added value: +"Max records, default 20"
    • addedInput schema / properties / mode / description
      Added value: +"artlist (articles) or timelinevol (volume)"
    • addedInput schema / properties / query / description
      Added value: +"GDELT query, e.g. \"Hong Kong\" or a company name"
    • changedInput schema / properties / timespan / description
      Previous value: -"e.g. 24h, 7d, 1m"New value: +"Lookback window, e.g. 24h, 7d, 1m"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Source payload; fields vary per tool",
+      "type": "object"
+    },
+    "retrievedAt": {
+      "description": "ISO-8601 timestamp of retrieval",
+      "type": "string"
+    },
+    "source": {
+      "description": "Human-readable upstream source name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "retrievedAt",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds useful auth context ('free, no key') and notes the two return shapes (article list vs. volume timeline) beyond the annotation set, though it omits rate-limit or pagination behavior.

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, front-loaded with purpose and return shape, then the sibling routing. Every clause earns its place with no 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?

With a rich annotation set, 100% schema coverage, and an output schema that handles return values, the description covers what remains: purpose, return modes, auth note, and sibling disambiguation. Nothing an agent needs to call it correctly 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 all four parameters are documented in the schema itself. The description only lightly reflects the mode parameter ('or a volume timeline') and adds no syntax or format detail beyond what the schema provides, so the 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?

States a specific verb (Search) and resource (GDELT DOC 2.0 global news), and explicitly contrasts itself with the sibling hn_search for tech-community discussion. An agent can distinguish it from other news/search siblings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit usage scenarios ('news-volume trends and cross-outlet coverage') and names an alternative tool with the condition that selects it ('use hn_search for tech-community discussion'). Nothing is left to inference for tool selection.

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

All Primary Sources 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