Skip to main content
Glama

Verified pay ranges for jobs with accommodation

salary_info
Read-onlyIdempotent

Verified minimum pay ranges (collective agreements and statutory minimum wages, with source and date) for hospitality work in a European country, plus the median pay of current Job & Stay listings there. Use when someone asks "what will I earn as a cook/waiter/receptionist in Switzerland/Austria/Italy/Spain...". Activities: kitchen, service, reception, housekeeping, mountain hut (free text accepted in many languages).

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

Input Schema

NameRequiredDescriptionDefault
countryYesISO country code or country name, e.g. CH, Austria, España
activityNoe.g. cook, waiter, reception, housekeeping, mountain hut, Koch, kok, cuoco

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 declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds provenance (source and date) plus data composition (statutory/collective minimums plus median of current listings). It does not discuss rate limits, authentication, or result formatting, but those gaps are smaller given 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?

The purpose is front-loaded, followed by a concrete usage trigger and activity vocabulary. It is compact but repeats some activity and country examples already present in the schema, so it is slightly less tight than a 5.

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 simple read-only lookup with two parameters and no output schema, the description covers what data is returned, where the minimum ranges come from, and what the median component represents. It leaves gaps around optional activity behavior and exact output/currency format, but the agent has enough to invoke it in the main use case.

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 country and activity parameters are already documented. The description still adds useful domain semantics: activity is free text in many languages and covers kitchen, service, reception, housekeeping, and mountain hut rather than a fixed enum. It also reinforces the European-country scope beyond the country parameter's ISO/name examples.

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 resource: verified minimum pay ranges from collective agreements and statutory minimum wages, plus median pay of current Job & Stay listings. It makes the hospitality/European-country scope explicit, which clearly separates it from apply_job, get_job, and search_jobs. It does not name a sibling as an alternative, so it falls just short of 5.

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?

It gives an explicit trigger phrase ('Use when someone asks ...') and lists example roles and countries. It does not state when not to use the tool or name alternatives, so it meets the clear-context level but not full when/when-not 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