APIVerve

Unemployment Rate

UnemploymentRate

Read-only

Unemployment Rate: Unemployment Rate looks up labor statistics by two- or three-letter ISO country code. It returns the country name, reporting year, and record count, with paid plans adding historical annual rates. With changes=true it also returns whether unemployment rose or fell, and on paid plans the previous year and its rate, the 1- and 5-year change in percentage points, and the 5-year high, low and average. (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": "UnemploymentRate"
  }
}

Input Schema

Name	Required	Description
`year`	No	Specific year to retrieve data for (1991-present). Returns latest if not specified.
`changes`	No	Include the change against the previous year, the 5-year change and the 5-year high, low and average rate
`country`	Yes	ISO country code (2 or 3 letter). Examples: US, USA, DE, DEU, GB, GBR

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open world), yet the description adds genuinely new behavior: paid plans unlock historical annual rates and multi-year statistics, and each call costs 2 credits. That credit cost and tier gating is exactly the kind of operational detail an agent cannot get from the annotations.

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?

A single front-loaded paragraph that leads with the lookup scope, then returns, then the optional change statistics and cost. The 'Unemployment Rate: Unemployment Rate' repetition of the title is small dead weight but the rest is dense and earns its place.

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?

For a three-parameter read-only lookup with an output schema, this covers scope, tier gating, cost, and the effect of the optional flag. The only real gap is an explicit statement of the default year and what happens for unsupported country codes or years outside 1991-present.

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 the baseline is 3; the description earns an extra point by spelling out what changes=true returns on paid plans (previous year and its rate, 1- and 5-year deltas in percentage points, 5-year high/low/average), which is more specific than the schema's one-line description. It also implies the default behavior without an explicit year (latest year), reinforcing the schema.

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?

States a specific verb and resource ('looks up labor statistics by two- or three-letter ISO country code') and names the exact return fields, so an agent can tell it apart from generic country lookups. It never contrasts itself with the many adjacent economics siblings (GDPData, InflationRate, PopulationData, MinimumWage), so it stops short of a 5.

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 parameter discussion (lookup by country code, optional year, optional changes) and the cost note hints at a paid-tier tradeoff. There is no explicit statement of when to prefer this tool over InflationRate, GDPData, or MinimumWage, and no prerequisites are mentioned.

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

All APIVerve tools Inspect

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.