apibase

Climate Extreme Indices

world-bank-cckp.climate.extremes

Read-onlyIdempotent

Get a derived extreme-climate index for a country: hot days over 35C/40C (hd35/hd40), frost days (fd), max consecutive dry/wet days (cdd/cwd), heavy precipitation days over 20mm (r20mm), or tropical nights (tr23). Defaults to the 1995-2014 observed baseline (scenario "historical"), or pass an SSP scenario + future period for a projection. Data: World Bank Climate Change Knowledge Portal (CMIP6 model ensemble), no auth required.

Input Schema

TableJSON Schema

Name	Required	Description
`index`	Yes	Extreme-climate index: "hd35"/"hd40" (annual count of days with max temp > 35°C/40°C), "fd" (frost days, min temp < 0°C), "cdd" (max consecutive dry days, precip < 1mm), "cwd" (max consecutive wet days, precip >= 1mm), "r20mm" (days with precip > 20mm), "tr23" (tropical nights, min temp > 23°C).
`period`	No	Future 20-year projection window, only used when scenario is not "historical". Defaults to "2040-2059".
`country`	Yes	Geography code: ISO3166 alpha-3 country code (e.g. "BRA", "USA", "IND"), or a special aggregate code such as "all_countries" (every country in one call) or "region_SAS" (South Asia region, admin1-level breakdown included — replace SAS with any World Bank region code).
`scenario`	No	"historical" (default) returns the 1995-2014 observed baseline. A CMIP6 SSP scenario ("ssp126"/"ssp245"/"ssp370"/"ssp585") returns a future projection for the period below.
`aggregation`	No	Time aggregation of the returned values. "annual" returns one value per year, "monthly" returns 12 values per year, "seasonal" returns 4 values per year (DJF/MAM/JJA/SON). Defaults to "annual".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, which are consistent with the description. The description adds behavioral context beyond annotations: 'no auth required' and the default 1995-2014 observed baseline. This provides useful information about access and defaults not captured in 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?

The description is concise and front-loaded: it states the purpose, lists indices, explains default and projection modes, and notes data source and auth in two sentences. No fluff; every sentence contributes to understanding how to invoke the tool.

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?

Given the presence of an output schema, the description need not explain return values. It covers the main usage aspects: index selection, country, scenario, period, and aggregation (implicitly via schema). It adequately describes what the tool does and how to request historical vs. projected data. A minor gap is not explicitly mentioning aggregation defaults, but the schema covers that.

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 input schema already documents all parameters in detail. The description reiterates the index meanings and defaults (e.g., historical scenario, period default) but does not add significant new semantics beyond what the schema provides. Per the rubric, baseline 3 applies when schema covers parameters thoroughly.

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 states a specific verb ('Get') and resource ('derived extreme-climate index for a country'), enumerates the supported indices (hd35, hd40, fd, etc.), and distinguishes itself from sibling climate tools by focusing on extremes. It clearly differentiates from world-bank-cckp.climate.normal and world-bank-cckp.climate.projection.

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 description explains the default behavior (historical baseline) and how to get projections by passing an SSP scenario and period. It implies this tool is for extremes, but does not explicitly name alternatives or state when not to use it. The context is clear enough for an agent to decide, but lacks explicit exclusions.

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

All apibase 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.