Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_context

Search recent GDELT news for sentences where all query terms co-occur within the last 72 hours. Filter by date range, domain, language, or quotations.

Instructions

Sentence-level co-occurrence search across recent GDELT coverage. Search recent (last 72 hours) GDELT-monitored news for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd of an absolute time window. Same formats as from.
fromNoStart of an absolute time window. Accepts YYYY-MM-DD, RFC3339, or GDELT's raw YYYYMMDDHHMMSS. Cannot be combined with timespan; GDELT caps this endpoint's window at 72 hours.
sortNoResult order.
queryYesGDELT query string. All terms must co-occur in the same sentence. Supports quoted phrases, (a OR b), domain:example.com.
domainNoConvenience domain filter, appended to the query as domain:VALUE.
is_quoteNoOnly return sentences GDELT identified as a quotation.
languageNoSource-language filter (GDELT's searchlang parameter). Space-segmented languages only (excludes CJK and similar).
timespanNoRelative time window ending now, e.g. 30min, 6h, 3d. Cannot be combined with from/to. GDELT caps this endpoint's window at 72 hours.
maxrecordsNoRows to return. GDELT's own hard cap is 200 for this endpoint (lower than gdelt-search's 250); there is no pagination cursor beyond it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "datedesc",
+  "dateasc"
+]
  2. Addedv1.16.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the 72-hour recency constraint, but it does not describe what the tool returns, whether results include article/sentence metadata, pagination behavior, or any side effects. The incomplete second sentence further limits transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core purpose, but it ends mid-sentence with 'for.', which is a structural defect. A broken sentence is not acceptable conciseness; it suggests truncation rather than deliberate brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 9-parameter tool with no output schema and no annotations, so the description must do substantial contextual work. It does not describe return values, result format, limits beyond 72 hours, or parameter interactions. The truncated description leaves an agent without enough information to confidently invoke the tool correctly.

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 description coverage is 100%, so the parameters are already well-documented. The description adds little beyond what the schema provides; the sentence-level co-occurrence concept is also already captured in the query parameter description. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action and resource: sentence-level co-occurrence search across recent GDELT coverage. It is understandable on its own, but it does not explicitly differentiate from siblings like gdelt_search or gdelt_timeline, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no explicit guidance about when to use this tool versus alternatives. The 'last 72 hours' and 'sentence-level co-occurrence' hints imply a use case, but there is no mention of exclusions, alternatives, or conditions that should route an agent to this tool.

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

Deploy Server

Other Tools