Skip to main content
Glama

Kollegia – ledige stillinger og lønn i Norge

Lønn i et yrke

salary_for_occupation
Read-onlyIdempotent

Salary statistics for an occupation in Norway: median monthly salary for full-time employees, lower and upper quartile and estimated hourly wage (Statistics Norway, SSB), plus the number of open positions on Kollegia and in Norway overall (NAV). With a location, adds the number of open jobs there. Links to the occupation page on kollegia.no. SSB salaries are national, not per location.

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": {
      "occupation": "<occupation>"
    },
    "name": "salary_for_occupation"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNoOptional. Norwegian municipality, city district or county, e.g. 'Bergen', 'Tromsø', 'Grünerløkka', 'Vestland', 'Oslo'. Regions like 'Nord-Norge' or 'Vestlandet' also work, and 'hjemmefra' gives remote jobs.
occupationYesOccupation in Norwegian, e.g. 'kokk', 'sykepleier', 'tømrer', 'regnskapsfører'.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteNo
salaryNo
locationNo
open_jobsYes
occupationYes
suggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the bar is lower. The description still adds meaningful behavior: the data provenance (Statistics Norway/SSB for salary, NAV and Kollegia for job counts) and the important caveat that salaries are national while location only affects job counts. It does not discuss caching, latency, or data vintage.

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?

Four dense sentences, front-loaded with the core deliverable, then sources, then the two location caveats. Nothing is filler, though the parenthetical source attributions add length that could be tightened.

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?

With an output schema present, the description need not enumerate return values, yet it still names the key metrics and their sources, plus the national-vs-local caveat that an agent would otherwise get wrong. For a 2-parameter read-only lookup, nothing needed for correct invocation is missing.

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, and the description genuinely exceeds it by explaining the effect of 'location' on the result (adds local open jobs) and stating that it does not change salary figures. That is real semantic value beyond the example lists in the schema.

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

Purpose5/5

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

States a specific resource (salary statistics for an occupation in Norway) and enumerates exactly what is produced: median monthly salary, quartiles, estimated hourly wage, plus open-position counts. This is unmistakably distinct from the job-search siblings (search_jobs, get_job, employer_jobs) without needing their schemas.

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 signals when to supply the optional location (to get local open-job counts) and clarifies the boundaries of the salary data ('SSB salaries are national, not per location'), which prevents a caller from expecting location-filtered salary. There is no explicit when-not-to-use or sibling routing, but the tool's domain is narrow and unambiguous.

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