Skip to main content
Glama

Gdelt

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. Description adds scoping by identifier, persistence differences for authenticated vs anonymous users. Does not mention overwrite behavior if same key is used again. No contradiction with annotations.

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 with no wasted words. Front-loaded with primary purpose, then context and alternatives. Every sentence adds value.

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?

Tool is simple with 2 params, no output schema. Description covers purpose, usage context, behavioral notes, and relationships with siblings. Complete for an AI agent to use correctly.

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?

Schema has 100% description coverage, so baseline is 3. Description adds context by giving example key patterns and explaining that value can be any text. Provides meaning beyond schema via scope and persistence info.

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 saves data for reuse, with concrete examples like 'resolved ticker', 'target address', 'user preference'. It distinguishes from siblings 'recall' and 'forget' by mentioning pairing.

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?

Explicitly says when to use: 'when you discover something worth carrying forward'. Mentions alternatives: 'Pair with recall to retrieve later, forget to delete.' Provides clear context for selection.

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.9/5.0
Disambiguation3/5

Several families overlap heavily—ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, and validate_claim all answer natural-language questions—and the five polymarket_* tools all circle around detecting or trading edges. However, detailed descriptions and distinct scopes (single vs multi-part vs grounded vs claim verdict, scan vs arbitrage vs fill risk) keep most boundaries usable.

Naming Consistency4/5

Names are uniformly snake_case and mostly follow a clear verb_noun or resource pattern (search_articles, compare_entities, list_subscriptions, remember/recall/forget). Minor deviations exist—ask_pipeworx has no underscore and some names are product-prefixed (pipeworx_trending, polymarket_edges)—but the overall pattern is still predictable.

Tool Count2/5

35 tools is well above the 25+ threshold, and the set spans unrelated domains—GDELT news, prediction markets, memory, subscriptions, npm dependency scanning, and llms.txt generation—so it feels like several servers mashed together rather than one coherent scope.

Completeness4/5

As a broad read-only data/research toolkit, coverage is strong: ask_pipeworx routes to thousands of sources, entity/compare/recent_changes/validate cover lookups, memory lifecycle is complete, and subscriptions have create/list/read/cancel. Minor gaps exist—no article-level GDELT aggregates beyond the four news tools and no direct update/delete for llms.txt—but there are no critical dead ends.

Resources