Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

GDP Data

GDPData
Read-only

GDP Data: Get GDP (Gross Domestic Product) data for any country including current values and historical data going back to 1960. With changes=true it also returns the direction against the previous year, and on paid plans the prior year's GDP, the dollar and percent change, whether real growth is accelerating or slowing, and 5- and 10-year compound annual growth. (Cost: 2 credits)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "GDPData"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoSpecific year to retrieve data for (1960-present). Returns latest if not specified.
changesNoInclude the change against the previous year, the growth trend, the 5-year average growth rate and the 5- and 10-year compound annual growth rates
countryYesISO 2 or 3-letter country code (e.g., US, USA, GB, GBR)

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, open-world lookup, and the description adds useful behavioral context: credit cost and paid-plan gating for richer change metrics. It does not explain every output detail, but the output schema exists and the important plan/cost behavior is disclosed.

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 two tightly written sentences, front-loads the core capability, and includes cost without wasting space. The parenthetical cost note is short and useful.

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 three-parameter read-only economic-data lookup, the description covers the covered time range, the important changes behavior, plan limitations, and cost. Since an output schema exists, it does not need to describe return values in detail.

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 parameter definitions are already present. The description still adds meaning beyond the schema by explaining that changes=true returns direction against the previous year and that additional metrics depend on paid-plan status.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: get GDP data for any country, including current values and historical data back to 1960. It is clear about scope, though it does not explicitly differentiate from nearby economic-data siblings such as PopulationData or InflationRate.

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?

Usage is implied by the stated resource and the changes=true option, but there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative tools. An agent can infer the context but is not actively routed.

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

All APIVerve 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