Skip to main content
Glama

Get Gdp

get_gdp
Read-onlyIdempotent

Fetch annual GDP in current USD (NY.GDP.MKTP.CD) for a country from the World Bank, defaulting to 2015-2024. Returns a year-by-year array of values. Shortcut for get_indicator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country_code": "DE"
    },
    "name": "get_gdp"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYesISO country code (e.g., "US", "GBR", "CN")

Output Schema

NameRequiredDescriptionDefault
dataYesTime-series GDP data in current USD sorted by year descending
countryYesCountry name or code
country_idYesWorld Bank country ID
date_rangeYesRequested date range in start:end format
indicator_idYesWorld Bank indicator code
last_updatedYesLast update timestamp from World Bank API
total_recordsYesTotal number of records available
indicator_nameYesFull indicator name/description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "country": {
      +      "description": "Country name or code",
      +      "type": "string"
      +    },
      +    "country_id": {
      +      "description": "World Bank country ID",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "data": {
      +      "description": "Time-series GDP data in current USD sorted by year descending",
      +      "items": {
      +        "properties": {
      +          "value": {
      +            "description": "GDP value in current USD for the year",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "year": {
      +            "description": "Year of the observation",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "date_range": {
      +      "description": "Requested date range in start:end format",
      +      "type": "string"
      +    },
      +    "indicator_id": {
      +      "description": "World Bank indicator code",
      +      "type": "string"
      +    },
      +    "indicator_name": {
      +      "description": "Full indicator name/description",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "last_updated": {
      +      "description": "Last update timestamp from World Bank API",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total_records": {
      +      "description": "Total number of records available",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "country",
      +    "country_id",
      +    "indicator_id",
      +    "indicator_name",
      +    "date_range",
      +    "total_records",
      +    "last_updated",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "country_code": "DE"
      +  }
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds the concrete data source, indicator code, default year window, and return shape (year-by-year array). The mention of a default window is slightly ambiguous since no year parameter exists to override it.

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?

Three short sentences: what is fetched, what is returned, and the sibling relationship. The indicator code is front-loaded and nothing is redundant.

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 one-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed: source, indicator identity, default range, and return shape. No material gap for an agent to call it correctly.

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?

The single parameter country_code already has a full schema description with ISO examples, so the schema carries the weight. The description adds context about the indicator and years but nothing that clarifies the country_code parameter itself, making the baseline 3 correct.

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 verb (Fetch), resource (annual GDP in current USD), data source (World Bank), and the exact indicator code NY.GDP.MKTP.CD. An agent can distinguish it from get_population or get_governance_indicators without opening the schema.

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?

"Shortcut for get_indicator" plus the explicit indicator code tells the agent when this tool suffices versus when the generic indicator tool is needed. It does not spell out a when-not condition or mention alternatives beyond get_indicator, so it falls short of full routing guidance.

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.