> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gdeltcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Tools
> 73 tools, reached through 42 — how progressive discovery works and what is in each category.
## The server does not expose one tool per endpoint
There are **73 tools**. Advertising them all would spend a large part of a model's context describing an API before it has been asked anything, and the value lists alone run past a thousand entries.
So each **category** exposes three thin tools instead — **42 in total** — and the model walks down only the branch it needs:
| Tool | What it does |
| ---------------------- | -------------------------------------------------- |
| `{category}_tool_list` | List what is in this category |
| `{category}_tool_get` | Fetch one tool's parameters, types and value lists |
| `{category}_tool_call` | Run it |
`{category}` is the category name from the table below — so the events tools are reached with `gdelt_cloud_tool_list`, `gdelt_cloud_tool_get` and `gdelt_cloud_tool_call`, and the maritime ones with `maritime_tool_list` and so on.
**The trio is per category, not global.** There is no single `tool_list`. Picking the category is the first decision, which is why each one below says when to reach for it.
The practical consequence for a model: fetch the schema with `_tool_get` **before** the first call to a tool it has not used in this conversation. Guessing a parameter name is the single most common failure, and the server rejects unknown filters rather than ignoring them.
## Categories
| Category | Tools | What it is for |
| -------------------------------------------------------------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`gdelt_cloud`](#gdelt-cloud) — GDELT Cloud | 13 | Real-world dynamics — what happened, who did it, where, and how often. The anchor category: coded events, clustered stories, resolved entities and the aggregates over them. Start here for any question about events rather than a static registry fact. |
| [`media_intel`](#media-intel) — Media Intelligence | 3 | How an entity is covered by the press — tone over time and share of voice against a peer set. |
| [`facilities`](#facilities) — Facilities | 3 | The unified physical-asset directory — power plants, industrial sites, ports and data centers on one keyed surface, resolved to spine owners. |
| [`gov`](#gov) — Government | 2 | US federal awards and foreign-influence registrations, resolved onto the entity spine. |
| [`filings`](#filings) — Filings | 7 | SEC EDGAR — the filing index, XBRL financials, and relations extracted from filing text. |
| [`gleif`](#gleif) — Legal Entities | 5 | The GLEIF Global LEI Index — legal-entity reference data, consolidation relationships and LEI↔ISIN mappings. |
| [`energy`](#energy) — Energy | 6 | Global Energy Monitor assets and the ownership registry over them. |
| [`epoch`](#epoch) — AI Compute | 5 | Epoch AI — models, hardware, data centers, companies and chip sales. |
| [`macro`](#macro) — Macro Finance | 4 | FRED economic series, with true point-in-time vintages rather than the latest revision. |
| [`risk`](#risk) — Risk and Screening | 7 | Restricted-party lists, name screening, ownership-chain exposure and China development finance. Analytical coverage, not an audit-grade compliance control. |
| [`maritime`](#maritime) — Maritime | 12 | AIS-derived vessel flow — chokepoint transits, port dwell, dark gaps and last-known positions. Terrestrial AIS only, so coverage thins in open ocean. |
| [`prediction_market`](#prediction-market) — Prediction Markets vendor | 4 | Kalshi contracts, read as a market-implied probability rather than a fact. A vendor surface reached through the same protocol — not GDELT Cloud data. |
| [`web_research`](#web-research) — Web Research vendor | 2 | Live web search and page extraction, for corroborating a finding against primary sources after the structured surfaces have answered. A vendor surface, not GDELT Cloud data. |
| [`macro_finance`](#macro-finance) — Macro Finance (vendor) vendor | — | Alpha Vantage market and economic series. Distinct from the `macro` category above, which is our FRED surface with point-in-time vintages — this one is a vendor passthrough. |
## GDELT Cloud
`gdelt_cloud` · Core
Real-world dynamics — what happened, who did it, where, and how often. The anchor category: coded events, clustered stories, resolved entities and the aggregates over them. Start here for any question about events rather than a static registry fact.
| Tool | |
| ----------------------- | --------------------------------- |
| `search_events` | |
| `summarize_events` | |
| `get_event` | |
| `search_stories` | |
| `summarize_stories` | |
| `get_story` | |
| `get_story_articles` | |
| `search_entities` | |
| `get_entity` | |
| `unified_entity_search` | |
| `get_entity_dossier` | Requires the matching entitlement |
| `intelligence_gpr` | Requires the matching entitlement |
| `list_admin1` | |
Parameters and value lists are the endpoint's own: see [Events](/api-reference) · [Stories](/api-reference) · [Entities](/api-reference) · [Unified Search](/api-reference) · [Geography](/api-reference) · [Atlas Intelligence](/api-reference) in the API reference, or fetch them at call time with `gdelt_cloud_tool_get`.
## Media Intelligence
`media_intel` · Core
How an entity is covered by the press — tone over time and share of voice against a peer set.
| Tool | |
| ---------------- | --------------------------------- |
| `entity_tone` | |
| `share_of_voice` | |
| `social_signal` | Requires the matching entitlement |
Parameters and value lists are the endpoint's own: see [Media Intelligence](/api-reference) in the API reference, or fetch them at call time with `media_intel_tool_get`.
## Facilities
`facilities` · Core
The unified physical-asset directory — power plants, industrial sites, ports and data centers on one keyed surface, resolved to spine owners.
| Tool | |
| --------------------- | - |
| `facilities_search` | |
| `facilities_get` | |
| `facilities_by_owner` | |
Parameters and value lists are the endpoint's own: see [Facilities](/api-reference) in the API reference, or fetch them at call time with `facilities_tool_get`.
## Government
`gov` · Open Feeds
US federal awards and foreign-influence registrations, resolved onto the entity spine.
| Tool | |
| ------------ | - |
| `gov_awards` | |
| `gov_fara` | |
Parameters and value lists are the endpoint's own: see [Government](/api-reference) in the API reference, or fetch them at call time with `gov_tool_get`.
## Filings
`filings` · Open Feeds
SEC EDGAR — the filing index, XBRL financials, and relations extracted from filing text.
| Tool | |
| ----------------------- | - |
| `filings_search` | |
| `filings_summary` | |
| `filings_get_filer` | |
| `filings_get_relations` | |
| `filings_get_facts` | |
| `filings_resolve` | |
| `filings_events` | |
Parameters and value lists are the endpoint's own: see [Filings](/api-reference) in the API reference, or fetch them at call time with `filings_tool_get`.
## Legal Entities
`gleif` · Open Feeds
The GLEIF Global LEI Index — legal-entity reference data, consolidation relationships and LEI↔ISIN mappings.
| Tool | |
| --------------------- | - |
| `gleif_entities` | |
| `gleif_entity` | |
| `gleif_relationships` | |
| `gleif_isin` | |
| `entity_hierarchy` | |
Parameters and value lists are the endpoint's own: see [Reference Data](/api-reference) in the API reference, or fetch them at call time with `gleif_tool_get`.
## Energy
`energy` · Open Feeds
Global Energy Monitor assets and the ownership registry over them.
| Tool | |
| ------------------------- | - |
| `energy_search_assets` | |
| `energy_summarize_assets` | |
| `energy_get_asset` | |
| `energy_assets_by_owner` | |
| `energy_search_owners` | |
| `energy_get_owner` | |
Parameters and value lists are the endpoint's own: see [Energy](/api-reference) in the API reference, or fetch them at call time with `energy_tool_get`.
## AI Compute
`epoch` · Open Feeds
Epoch AI — models, hardware, data centers, companies and chip sales.
| Tool | |
| -------------------- | - |
| `epoch_models` | |
| `epoch_hardware` | |
| `epoch_data_centers` | |
| `epoch_companies` | |
| `epoch_chip_sales` | |
Parameters and value lists are the endpoint's own: see [AI Compute](/api-reference) in the API reference, or fetch them at call time with `epoch_tool_get`.
## Macro Finance
`macro` · Open Feeds
FRED economic series, with true point-in-time vintages rather than the latest revision.
| Tool | |
| --------------------- | - |
| `macro_search_series` | |
| `macro_get_series` | |
| `macro_observations` | |
| `macro_releases` | |
Parameters and value lists are the endpoint's own: see [Macro Finance](/api-reference) in the API reference, or fetch them at call time with `macro_tool_get`.
## Risk and Screening
`risk` · Open Feeds
Restricted-party lists, name screening, ownership-chain exposure and China development finance. Analytical coverage, not an audit-grade compliance control.
| Tool | |
| ------------------------ | - |
| `screening_match` | |
| `exposure_search` | |
| `lists_catalog` | |
| `list_entries_search` | |
| `lists_changes` | |
| `china_projects_search` | |
| `china_projects_summary` | |
Parameters and value lists are the endpoint's own: see [Screening and Reference](/api-reference) · [China](/api-reference) in the API reference, or fetch them at call time with `risk_tool_get`.
## Maritime
`maritime` · Open Feeds
AIS-derived vessel flow — chokepoint transits, port dwell, dark gaps and last-known positions. Terrestrial AIS only, so coverage thins in open ocean.
| Tool | |
| --------------------------- | - |
| `maritime_chokepoint_watch` | |
| `maritime_transits` | |
| `maritime_vessels` | |
| `maritime_vessel_track` | |
| `maritime_get_carrier` | |
| `maritime_ports` | |
| `maritime_port_pulse` | |
| `maritime_dwell` | |
| `maritime_gaps` | |
| `maritime_activity` | |
| `maritime_density` | |
| `maritime_tracks` | |
Parameters and value lists are the endpoint's own: see [Maritime](/api-reference) in the API reference, or fetch them at call time with `maritime_tool_get`.
## Prediction Markets
`prediction_market` · Vendor
Kalshi contracts, read as a market-implied probability rather than a fact. A vendor surface reached through the same protocol — not GDELT Cloud data.
| Tool | |
| ------------------------- | - |
| `SEARCH_RELEVANT_MARKETS` | |
| `SEARCH_EVENTS` | |
| `SEARCH_MARKETS` | |
| `GET_MARKET` | |
## Web Research
`web_research` · Vendor
Live web search and page extraction, for corroborating a finding against primary sources after the structured surfaces have answered. A vendor surface, not GDELT Cloud data.
| Tool | |
| ------------------- | - |
| `SEARCH_WEB` | |
| `EXTRACT_WEB_PAGES` | |
## Macro Finance (vendor)
`macro_finance` · Vendor
Alpha Vantage market and economic series. Distinct from the `macro` category above, which is our FRED surface with point-in-time vintages — this one is a vendor passthrough.
The catalog for this category is fetched from the provider at call time, so there is no fixed list to publish — ask `macro_finance_tool_list` for the current one. Reached through the same protocol, but not GDELT Cloud data — see [External tools](/mcp/external-tools).
## What is metered
A `_tool_call` costs the same as the REST call it makes, against the same plan limits, and appears in the same usage reporting. `_tool_list` and `_tool_get` are discovery and are not metered. An endpoint your entitlement does not include returns an error naming what it needs — never an empty result, which would be indistinguishable from missing data.