Skip to main content
Glama

Get Poverty Regional

get_poverty_regional
Read-onlyIdempotent

Aggregated World Bank poverty estimates at the regional/group level (not per-country). Returns headcount, poverty gap, mean welfare, and total population in poverty for each group. group_by controls the aggregation: "wb" = World Bank geographic regions, "inc" = income groups (HIC/UMIC/LMIC/LIC), "none" = global total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoReporting year (e.g. "2020") or "all". Default "all".
povlineNoPoverty line in $/day (2017 PPP). Common values: 2.15, 3.65, 6.85. Default 2.15.
group_byNoAggregation: "wb" geographic regions, "inc" income groups, "none" global total. Default "wb".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "group_by": "wb",
      +    "povline": 2.15,
      +    "year": "2020"
      +  },
      +  {
      +    "group_by": "inc",
      +    "povline": 6.85,
      +    "year": "all"
      +  }
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds that it returns headcount, poverty gap, mean welfare, and total population, providing behavioral detail beyond annotations without contradiction.

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 three sentences, front-loaded with the main purpose, with no unnecessary words. Every sentence adds essential information.

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?

No output schema, but the description lists return values. No missing critical information for a simple query tool with clear parameters and annotations.

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%, so baseline is 3. The description adds value by elaborating on group_by values and common poverty lines, enhancing understanding 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 clearly states it returns aggregated World Bank poverty estimates at the regional/group level, not per-country. It specifies the verb 'returns' and the resource, and distinguishes from sibling tools like get_poverty.

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?

The description explicitly explains when to use each group_by value: 'wb' for geographic regions, 'inc' for income groups, 'none' for global total. This provides clear guidance on aggregation choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.