Skip to main content
Glama
Satyampatel779

country-analytics-mcp

by Satyampatel779
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

region_total

Sum GDP or population, or calculate population-weighted GDP per capita, for a continent or region; choose year, scope, currency, and missing-data policy.

Instructions

Regional total for a continent: sum of GDP, sum of population, or population-weighted GDP per capita (sum GDP / sum population). All judgment calls are parameters:

  • scope: 'continent' = the geographic continent per the country-list source (default); 'wb_region' = the World Bank region(s) overlapping it — a DIFFERENT country set (e.g. Europe & Central Asia adds Central Asia and the Caucasus).

  • year: "2022" or "latest" (latest walks back per country and may mix years — flagged).

  • missing_policy (pinned years): 'exclude' = countries without that year's value are excluded and listed (default); 'walk_back' = use their most recent earlier value.

  • currency / fx_date: as in get_country_metric. The response lists every included country with its value and year, every exclusion with its reason, the FX rate used, and the assumptions applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNolatest
scopeNocontinent
metricNogdp
fx_dateNo
currencyNoUSD
continentYes
missing_policyNoexclude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does notably well: it discloses that 'latest' walks back per country and may mix years (flagged), that exclusions are listed, and that FX rate and assumptions are returned. It doesn't cover permissions, rate limits, or pagination, but for an analytical aggregation those are less critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the computation in the first sentence, then a clean bulleted parameter list. Slightly dense, and 'All judgment calls are parameters' is a filler clause, but overall tight and scannable.

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

Completeness5/5

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

For a 7-parameter aggregation with no output schema and no annotations, the description covers the computation, every judgment-call parameter, default behaviors, and even the response contents (included countries, exclusions, FX rate, assumptions). Nothing essential to correct invocation is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate and it does: it defines scope='continent' vs 'wb_region' (with a concrete example of the differing country set), year='latest' behavior, missing_policy='exclude' vs 'walk_back' semantics, and defers currency/fx_date to get_country_metric. It documents nearly all 7 parameters beyond bare titles.

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?

States a specific computation ('sum of GDP, sum of population, or population-weighted GDP per capita') over a named resource (continent region). It clearly distinguishes itself from siblings like get_country_metric (single country) and rank_countries (ordering), so an agent can route correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains parameter semantics well but never says when to prefer this tool over get_country_metric or rank_countries, nor when a region total is the right call. Usage is implied by the computation described, but no explicit when/when-not guidance is given.

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

Deploy Server

Other Tools