Skip to main content
Glama

worlduank

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Country Co2 Emissions

country_co2_emissions
Read-onlyIdempotent

National CO2 emissions for ANY country worldwide, annual, from the World Bank (AR5 basis, excluding LULUCF). PREFER for "CO2 emissions of ", "how much CO2 does emit", "carbon emissions by country", "rank countries by CO2", " emissions per capita", "CO2 emissions trend for ". Pass one country for a year-by-year series, or several to rank them high→low. Set per_capita for tonnes per person. NOTE: other emissions tools in this catalog are US-only (EPA facility/sector data) or electricity grid-intensity — this is the one for country-level national totals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_rangeNoYear range "start:end" (default "2015:2024"). Example: "2000:2024".
per_capitaNoReturn tonnes of CO2 per person instead of national totals (computed from population for the same year). Default false.
country_codesYesOne or more ISO country codes, comma- or semicolon-separated (e.g. "BR", "US,CN,IN"). Also accepts "WLD" for the world total.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_codes": "IN"
+  },
+  {
+    "country_codes": "US,CN,DE,BR",
+    "date_range": "2000:2024",
+    "per_capita": true
+  }
+]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive. Description adds data source (World Bank, AR5 basis, excluding LULUCF) and annual frequency, which are helpful beyond annotations. No contradictions.

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?

Highly efficient: three sentences cover purpose, usage patterns, and sibling differentiation. Front-loaded with core function. No fluff.

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?

Tool is simple with 3 params and no output schema. Description covers how to invoke and differentiate, but does not explain return format (e.g., columns, units). Still, minimal gaps given the tool's straightforward nature.

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 coverage is 100% with good descriptions. The description adds value beyond schema: clarifies ranking vs. time series, reinforces per_capita meaning, and provides usage examples. Not redundant.

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?

Specific verb and resource ('National CO2 emissions for ANY country worldwide') immediately identifies purpose. Distinguishes from sibling tools by noting other emissions tools are US-only or grid-intensity. No ambiguity.

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 states when to prefer this tool with example queries. Provides clear usage patterns: pass one country for time series, several for ranking. Notes exclusion of other tools, giving full guidance.

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

All worlduank toolsInspect
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