Skip to main content
Glama

Compare European countries on one indicator

compare_countries
Read-onlyIdempotent

Ranks European countries by the latest figure of one indicator: inflation, unemployment, GDP growth, minimum wage, average salary, petrol and diesel prices, household electricity and gas prices, mortgage and deposit rates, government debt, house prices and more. Each row has the country, the value and the period it refers to.

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": {
      "indicator": "<indicator>"
    },
    "name": "compare_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
indicatorYesWhat to compare, for example inflation, unemployment, minimum-wage, average-salary, petrol-prices, electricity-prices, mortgage-rates, government-debt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description does add value beyond them by disclosing the output shape (each row has country, value and reference period) and the ranking/latest-figure behavior, but it omits the sort direction and how many countries are returned.

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?

Two sentences, front-loaded with the core action; the trailing 'and more' list is somewhat redundant with the enum but aids discoverability of indicator coverage. No filler sentences.

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 single-parameter, read-only ranking tool with no output schema, the description covers what it does, the indicator scope, and the row structure. It notes that each row carries its own period, implicitly handling countries with differing latest data points; sort order and country coverage remain unstated but are minor.

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% with a fully enumerated indicator parameter, so the baseline is a 3. The description goes slightly further by restating representative indicator names and clarifying that only the latest figure is used, reinforcing that this is a single-indicator selection rather than a time-range parameter.

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: it ranks European countries by the latest value of one indicator, and enumerates examples of that indicator. This clearly separates it from the single-metric siblings (get_inflation, get_fuel_prices) as a cross-country ranking tool, though the description never names those siblings explicitly.

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 rather than stated: 'ranks European countries' signals cross-country comparison, and 'latest figure' implicitly excludes historical/time-series requests. There is no explicit when-to-use or when-to-prefer-a-sibling 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.

Resources