Skip to main content
Glama

Minimum wage and average salary

get_wages
Read-onlyIdempotent

The national statutory minimum wage (gross, euro per month, the rate in force on 1 January or 1 July) and the average full-time adjusted gross annual salary of one European country, from Eurostat. Says so when a country has no statutory minimum wage.

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": "get_wages"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-2 country code (Greece is GR), or EA for the euro area

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior. Beyond that, the description adds real value: it discloses the units (gross euro per month), the reference timing of the rate (1 January or 1 July), the source (Eurostat), and — importantly — that it reports when a country has no statutory minimum wage, which tells the agent how missing data manifests.

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 dense sentence that front-loads the primary metric and packs units, timing, and source without filler. The mid-sentence parenthetical makes it slightly harder to parse, but no clause is wasted.

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?

The tool is simple (one enum parameter, no output schema), so the description must carry return-value meaning, and it does: both metrics, their units, and the missing-minimum-wage case are stated. Minor gaps remain around time coverage of the salary figure and output shape, but nothing essential to correct invocation is missing.

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?

Schema coverage is 100%, and the single enum parameter already documents the ISO alpha-2 codes, the Greece=GR caveat, and the EA euro-area option. The description reinforces that only one country is queried but adds no format or edge-case detail about the parameter beyond the schema, so baseline 3 applies.

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 names the exact resources returned — the national statutory minimum wage (gross, euro/month, rate in force on 1 Jan or 1 July) and the average full-time adjusted gross annual salary — for one European country, sourced from Eurostat. It is specific enough to distinguish it from siblings like get_inflation or compare_countries by the resource and single-country scope, though it never names a sibling 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: 'of one European country' signals single-country lookups, which implicitly contrasts with compare_countries, but there is no explicit when-to-use or when-not-to-use guidance. An agent must infer the retrieval context from the resource description alone.

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