worldgdp.org GDP nowcasts

get_nowcast

Current GDP nowcast for one economy: headline (% SAAR), 70% range, days to official release, recent daily path, component contributions and the latest data releases that moved it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "economy": "<economy>"
    },
    "name": "get_nowcast"
  }
}

Input Schema

Name	Required	Description
`days`	No	Length of daily path to return
`economy`	Yes	Economy code: us (United States), cn (China), jp (Japan), de (Germany), in (India), uk (United Kingdom), fr (France), it (Italy), ca (Canada), br (Brazil), es (Spain), mx (Mexico), kr (South Korea), au (Australia), nl (Netherlands), ch (Switzerland), pl (Poland), be (Belgium), se (Sweden), ie (Ireland), at (Austria), pt (Portugal), fi (Finland), gr (Greece), dk (Denmark), no (Norway), ro (Romania), bg (Bulgaria), tr (Türkiye), ru (Russia), id (Indonesia), th (Thailand), sg (Singapore), tw (Taiwan), hk (Hong Kong), my (Malaysia), ph (Philippines), nz (New Zealand), ar (Argentina), co (Colombia), cl (Chile), sa (Saudi Arabia), kw (Kuwait), ae (United Arab Emirates), eg (Egypt), ma (Morocco), za (South Africa), ng (Nigeria)
`quarter`	No	e.g. 2026Q3; defaults to the current quarter. The last 6 quarters are available (released ones as archived final nowcasts with the official first estimate)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / economy / description

Previous value: -"Economy code: us (United States), cn (China), jp (Japan), de (Germany), in (India), uk (United Kingdom), fr (France), it (Italy), ca (Canada), br (Brazil), es (Spain), mx (Mexico), kr (South Korea), au (Australia), nl (Netherlands), ch (Switzerland), pl (Poland), be (Belgium), se (Sweden), ie (Ireland), at (Austria), pt (Portugal), fi (Finland), gr (Greece), dk (Denmark), no (Norway), ro (Romania), bg (Bulgaria), tr (Türkiye), ru (Russia), id (Indonesia), th (Thailand), sg (Singapore), hk (Hong Kong), my (Malaysia), ph (Philippines), nz (New Zealand), ar (Argentina), co (Colombia), cl (Chile), sa (Saudi Arabia), kw (Kuwait), ae (United Arab Emirates), eg (Egypt), ma (Morocco), za (South Africa), ng (Nigeria)"New value: +"Economy code: us (United States), cn (China), jp (Japan), de (Germany), in (India), uk (United Kingdom), fr (France), it (Italy), ca (Canada), br (Brazil), es (Spain), mx (Mexico), kr (South Korea), au (Australia), nl (Netherlands), ch (Switzerland), pl (Poland), be (Belgium), se (Sweden), ie (Ireland), at (Austria), pt (Portugal), fi (Finland), gr (Greece), dk (Denmark), no (Norway), ro (Romania), bg (Bulgaria), tr (Türkiye), ru (Russia), id (Indonesia), th (Thailand), sg (Singapore), tw (Taiwan), hk (Hong Kong), my (Malaysia), ph (Philippines), nz (New Zealand), ar (Argentina), co (Colombia), cl (Chile), sa (Saudi Arabia), kw (Kuwait), ae (United Arab Emirates), eg (Egypt), ma (Morocco), za (South Africa), ng (Nigeria)"

changedInput schema / properties / economy / enum

Previous value: -[
-  "us",
-  "cn",
-  "jp",
-  "de",
-  "in",
-  "uk",
-  "fr",
-  "it",
-  "ca",
-  "br",
-  "es",
-  "mx",
-  "kr",
-  "au",
-  "nl",
-  "ch",
-  "pl",
-  "be",
-  "se",
-  "ie",
-  "at",
-  "pt",
-  "fi",
-  "gr",
-  "dk",
-  "no",
-  "ro",
-  "bg",
-  "tr",
-  "ru",
-  "id",
-  "th",
-  "sg",
-  "hk",
-  "my",
-  "ph",
-  "nz",
-  "ar",
-  "co",
-  "cl",
-  "sa",
-  "kw",
-  "ae",
-  "eg",
-  "ma",
-  "za",
-  "ng"
-]New value: +[
+  "us",
+  "cn",
+  "jp",
+  "de",
+  "in",
+  "uk",
+  "fr",
+  "it",
+  "ca",
+  "br",
+  "es",
+  "mx",
+  "kr",
+  "au",
+  "nl",
+  "ch",
+  "pl",
+  "be",
+  "se",
+  "ie",
+  "at",
+  "pt",
+  "fi",
+  "gr",
+  "dk",
+  "no",
+  "ro",
+  "bg",
+  "tr",
+  "ru",
+  "id",
+  "th",
+  "sg",
+  "tw",
+  "hk",
+  "my",
+  "ph",
+  "nz",
+  "ar",
+  "co",
+  "cl",
+  "sa",
+  "kw",
+  "ae",
+  "eg",
+  "ma",
+  "za",
+  "ng"
+]

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / quarter / description

Previous value: -"e.g. 2026Q3; defaults to the current quarter"New value: +"e.g. 2026Q3; defaults to the current quarter. The last 6 quarters are available (released ones as archived final nowcasts with the official first estimate)"

Changed2 schema fields changedOct 23, 2026

changedInput schema / properties / economy / description

Previous value: -"Economy code: us (United States), cn (China), jp (Japan), de (Germany), in (India), uk (United Kingdom), fr (France), it (Italy), ca (Canada), br (Brazil), es (Spain), mx (Mexico), kr (South Korea), au (Australia), nl (Netherlands), ch (Switzerland), pl (Poland), be (Belgium), se (Sweden), ie (Ireland), at (Austria), pt (Portugal), fi (Finland), gr (Greece), dk (Denmark), no (Norway), ro (Romania), bg (Bulgaria), tr (Türkiye), ru (Russia), id (Indonesia), th (Thailand), sg (Singapore), hk (Hong Kong), my (Malaysia), ph (Philippines), nz (New Zealand), ar (Argentina), co (Colombia), cl (Chile), sa (Saudi Arabia), kw (Kuwait), eg (Egypt), ma (Morocco), za (South Africa), ng (Nigeria)"New value: +"Economy code: us (United States), cn (China), jp (Japan), de (Germany), in (India), uk (United Kingdom), fr (France), it (Italy), ca (Canada), br (Brazil), es (Spain), mx (Mexico), kr (South Korea), au (Australia), nl (Netherlands), ch (Switzerland), pl (Poland), be (Belgium), se (Sweden), ie (Ireland), at (Austria), pt (Portugal), fi (Finland), gr (Greece), dk (Denmark), no (Norway), ro (Romania), bg (Bulgaria), tr (Türkiye), ru (Russia), id (Indonesia), th (Thailand), sg (Singapore), hk (Hong Kong), my (Malaysia), ph (Philippines), nz (New Zealand), ar (Argentina), co (Colombia), cl (Chile), sa (Saudi Arabia), kw (Kuwait), ae (United Arab Emirates), eg (Egypt), ma (Morocco), za (South Africa), ng (Nigeria)"

changedInput schema / properties / economy / enum

Previous value: -[
-  "us",
-  "cn",
-  "jp",
-  "de",
-  "in",
-  "uk",
-  "fr",
-  "it",
-  "ca",
-  "br",
-  "es",
-  "mx",
-  "kr",
-  "au",
-  "nl",
-  "ch",
-  "pl",
-  "be",
-  "se",
-  "ie",
-  "at",
-  "pt",
-  "fi",
-  "gr",
-  "dk",
-  "no",
-  "ro",
-  "bg",
-  "tr",
-  "ru",
-  "id",
-  "th",
-  "sg",
-  "hk",
-  "my",
-  "ph",
-  "nz",
-  "ar",
-  "co",
-  "cl",
-  "sa",
-  "kw",
-  "eg",
-  "ma",
-  "za",
-  "ng"
-]New value: +[
+  "us",
+  "cn",
+  "jp",
+  "de",
+  "in",
+  "uk",
+  "fr",
+  "it",
+  "ca",
+  "br",
+  "es",
+  "mx",
+  "kr",
+  "au",
+  "nl",
+  "ch",
+  "pl",
+  "be",
+  "se",
+  "ie",
+  "at",
+  "pt",
+  "fi",
+  "gr",
+  "dk",
+  "no",
+  "ro",
+  "bg",
+  "tr",
+  "ru",
+  "id",
+  "th",
+  "sg",
+  "hk",
+  "my",
+  "ph",
+  "nz",
+  "ar",
+  "co",
+  "cl",
+  "sa",
+  "kw",
+  "ae",
+  "eg",
+  "ma",
+  "za",
+  "ng"
+]

First observedOct 17, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the uncertainty range, release countdown, daily path, contributions, and revision-driving releases, but does not explicitly establish read-only behavior or discuss freshness, sourcing, or failure behavior.

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?

One compact sentence front-loads the resource and scope, then efficiently inventories the returned information. Every listed item helps set expectations, with no filler or repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter getter without an output schema, the description supplies enough output detail to support selection and interpretation, while the schema fully documents invocation. Explicit sibling routing and clarification of current versus archived-quarter use would improve completeness, but neither is essential for a basic call.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. Phrases such as 'one economy' and 'recent daily path' reinforce economy and days, but the description adds no parameter defaults, constraints, or quarter-selection semantics 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 identifies the exact resource, a current GDP nowcast, and its scope, one economy. Listing outputs such as the headline (% SAAR), component contributions, and releases that moved the estimate also distinguishes it from broader siblings like get_aggregate and get_weekly_pulse.

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?

The single-economy, current-GDP framing gives clear context for when to select this tool. It does not explicitly name alternatives or exclusions, and the emphasis on 'current' does not surface the schema's support for archived nowcasts from earlier quarters.

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

All worldgdp.org GDP nowcasts tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?