Skip to main content
Glama

Gdelt

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description details the tool's behavior: it fans out to multiple sources, explains the GDELT→GNews fallback, mentions the USPTO soft-fail due to API sunset, and states the return structure (changes grouped by source, total_changes count, citation URIs). This goes well beyond the annotations which only indicate read-only, idempotent, etc.

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

Conciseness4/5

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

The description is a single paragraph that efficiently conveys purpose, sources, parameter details, and sibling distinction. It is front-loaded with the core action. Minor improvement could be adding bullet points for readability, but it's still concise and well-structured.

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?

Despite no output schema, the description adequately explains the return format (changes grouped by source, total count, citation URIs). It also covers edge cases like the USPTO soft-fail. The description is complete for the tool's 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?

While the input schema already describes all parameters (100% coverage), the description adds helpful context: examples of ISO dates and relative shorthand for 'since', and that 'value' accepts ticker or CIK. This adds value beyond the 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?

The description clearly states the tool provides a change feed for a company by querying multiple sources (SEC EDGAR, GDELT/GNews, USPTO). It includes example queries and explicitly distinguishes from the sibling tool 'entity_profile'.

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?

The description gives explicit usage scenarios ('What's new with X') and directly tells when to use the sibling tool 'entity_profile' instead. It also describes fallback behavior between GDELT and GNews.

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

Multiple tools have unclear boundaries: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), and ask_pipeworx_grounded are near-duplicates, while deep_research, entity_profile, compare_entities, and bet_research all route into the same underlying Pipeworx catalog. ai_visibility_check and scan_competitor_ai_presence also overlap heavily. Descriptions are detailed, but an agent could easily misselect among the research and market-analysis clusters.

Naming Consistency3/5

All names use lowercase snake_case, but the pattern is mixed: verb-first names (search_articles, resolve_entity, validate_claim), noun-phrase domain tools (entity_profile, polymarket_fill_risk), brand-prefixed names (pipeworx_trending, ask_pipeworx), and bare verbs (recall, remember, forget). It is readable and consistent in style, but there is no predictable verb_noun convention and tool names do not reliably indicate their domain.

Tool Count2/5

With 35 tools, this set is well beyond the 3-15 well-scoped range and even the 16-25 heavy range. Several clusters could be consolidated (three ask_pipeworx variants, five polymarket analysis tools, three memory tools), and unrelated utilities like generate_llms_txt and scan_dependency add to the sprawl.

Completeness4/5

For a data-research server, coverage is broad: universal lookup, grounded answers, deep research, entity profiles, comparisons, news search/sentiment/timelines, prediction-market analysis, and memory/subscription lifecycle tools are all present. The main gaps are direct raw-document fetching (e.g., full article text or a specific SEC filing body), but the universal ask_pipeworx router and pipeworx:// resource URIs let agents work around those.

Resources