GDELT Cloud Briefs are structured intelligence products generated by the hosted Brief agent and rendered as shareable Web Brief reports.The Brief agent does not improvise its own report format. It preloads:
gdelt_brief_system_prompt from the MCP server
the shared Brief tradecraft skill from MCP resources
the selected Brief production skill from MCP resources
the matching briefs.v1 structured content schema from the shared contracts package
The model populates only the analysis/content fields. Runtime software appends deterministic metadata, citations, appendix/tool diagnostics, run IDs, share/export state, and persistence fields.
GDELT Cloud Events provide the structured signal. GDELT Cloud Stories provide the narrative and source/article layer. External MCP categories enrich the analysis when relevant:
External category
Use in Briefs
web_research_*
Official statements, emergency guidance, port/maritime advisories, procurement pages, source extraction, and corroboration.
macro_finance_*
Commodities, FX, rates, equities, shipping, energy, sovereign-risk, and sector-channel exposure.
prediction_market_*
Market-implied probability context only when the contract maps cleanly to the scenario. Never use markets as ground truth.
Open-web AIS, ADS-B, ports, USAspending, SAM.gov, Open Contracting, Global Fishing Watch, OpenSky, PortWatch, and similar sources are treated as corroboration targets through web_research_* until GDELT Cloud exposes normalized native connectors for them.Briefs should preserve visual evidence from tool payloads when available. Event and Story cards can carry top-article image_url, article domain_avatar_url, and linked Entity image_url / avatar_url. Entity tools can carry Wikipedia thumbnail metadata. These fields should improve reader orientation and source recognition, not substitute for analytic evidence.For time-series panels, Brief agents should collect real history:
GDELT Cloud summaries: call summarize_events or summarize_stories with group_by=date over a recent window such as 14 or 30 days, then compare the current bucket against baseline or prior buckets.
Macro finance: use provider-supported historical or series tools; normalized outputs expose series, latest_value, and latest_date when history is available.
Prediction markets: use include_history=true where available; normalized outputs may expose probability_series.
Do not render or describe two-point placeholder trends as meaningful analysis. If a tool only returns a current value, say that the series is unavailable and use the value as context, not proof.
Validates inputs, starts one-off or scheduled Brief runs, persists artifacts, renders Web Brief reports, and manages sharing.
Database/cron
Stores Briefs, schedules, batches, runs, share keys, plan limits, and usage logs.
Agents and frontend code should know only stable MCP identifiers such as prompt names, skill URIs, and tool category tags. The details of GDELT Cloud tool schemas and analysis tradecraft live in MCP.
Direct MCP access and hosted agent access are metered differently:
Caller
Usage source
QU per MCP data tool call
User’s own MCP client, ChatGPT connector, Claude connector, or custom LangChain agent
mcp
1 QU
GDELT Cloud Agent UI
agent
3 QU
GDELT Cloud hosted Brief agent, including scheduled Briefs
brief
3 QU
The multiplier applies to GDELT Cloud data tools and external MCP categories. It reflects hosted orchestration, rendering, export generation, and backend agent execution.