Skip to main content
Glama

Gdelt

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.8/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds behavioral context: mark_read:true flags events as read, returns only newer ones on next call. No contradictions. Also describes feed persistence and alternative access.

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 sentences, front-loaded with main action, no unnecessary words. Each sentence adds value: purpose, return fields, filtering/mark_read, and alternative access.

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 parameter-rich list tool (5 optional params, no output schema), description covers return fields, filtering, mark_read behavior, polling suitability, and alternative endpoint. Complete enough for an agent to use correctly.

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

Parameters5/5

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

Schema coverage is 100%, and description adds concrete examples: 'Filter by type (e.g. "sec_8k")', 'since (ISO timestamp)', 'set mark_read:true to flag returned events read'. This provides practical usage beyond schema.

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?

Description clearly states it pulls fired events from subscription feed. It specifies return fields (source, citation_uri, raw payload) and filtering options. The tool is distinct from siblings like list_subscriptions or search_articles.

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?

Description says 'polls work fine' and mentions alternative endpoint for scripts/dashboards, implying when to use tool vs. direct API. However, it does not explicitly contrast with siblings like search_articles or list_subscriptions for similar use cases.

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

All Gdelt toolsInspect
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.

TDQS

A3.8/5.0
Disambiguation2/5

Several tools are near-duplicates: ask_pipeworx_beta is explicitly identical to ask_pipeworx, and discover_tools/suggest_questions plus entity_profile/recent_changes/compare_entities/validate_claim overlap in purpose. An agent selecting among the five ask/deep-research variants or six Polymarket tools will frequently need to read lengthy descriptions to avoid picking the wrong one.

Naming Consistency3/5

Most names are readable snake_case and clear verb_noun phrases like search_articles, resolve_entity, and validate_claim, with helpful families like polymarket_* and timeline_*. However, several tools are bare noun phrases (entity_profile, recent_alerts, pipeworx_trending, tone_distribution), and the memory trio (remember/recall/forget) breaks the domain-prefix pattern.

Tool Count2/5

35 tools is past the 25+ threshold and feels bloated for a server nominally about GDELT; much of the surface is meta/utility tooling (diagnostics, memory, discovery, subscriptions) rather than core news retrieval. Several tools could be consolidated, such as ask_pipeworx_beta and the multiple Polymarket edge/arb/research variants.

Completeness4/5

For its broad data/news/prediction-market scope, the surface is quite complete: GDELT search, volume, tone, and distribution are covered, along with entity resolution, company profiles, comparisons, claim verification, and trade-side analytics. Minor gaps exist, such as no full-text article fetch or direct GDELT raw-event export, but agents can mostly work around them.

Resources