Skip to main content
Glama

SourceGeek

Search ESCO occupations and skills

esco_search
Read-only

Search the European Commission's ESCO classification (European Skills, Competences, Qualifications and Occupations) for occupations or skills matching a job title, synonym, or skill name in any ESCO language. Returns ranked matches with their ESCO URI, preferred title, the label that matched, and (for occupations) the ISCO-based ESCO code.

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": {
      "query": "<query>"
    },
    "name": "esco_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoSearch occupations (job roles) or skills (skills, competences and knowledge). Defaults to occupation.occupation
limitNoNumber of matches to return (1-50, default 10).
queryYesJob title, occupation synonym, or skill to look up, e.g. 'software developer', 'IC-verpleegkundige', 'Python'.
offsetNoWhich page of matches to return, counting from 0. Each page holds `limit` matches.
languageNoISO 639-1 language for labels and descriptions (e.g. 'nl', 'de', 'fr'). Defaults to 'en'. Match the user's language when they search in it.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: results are ranked, and each match carries the ESCO URI, preferred title, the matched label, and an ISCO-based code for occupations. It does not mention rate limits or exhaustive-versus-truncated result behavior.

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?

Front-loaded with the core action and resource, followed by a compact sentence on return contents. The parenthetical expansion of the ESCO acronym is slightly verbose, but no sentence is redundant.

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?

There is no output schema, and the description compensates by enumerating the returned fields and noting ranking. Combined with a fully documented five-parameter schema, the definition gives enough to call the tool correctly; only ambiguity handling and result exhaustiveness are left implicit.

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 description coverage is 100%, with per-parameter descriptions for query, type, limit, offset and language, so the schema carries the parameter burden. The description only reinforces the language and query semantics ('in any ESCO language', 'job title, synonym, or skill name') without adding format or ranking details not already 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?

The description names a specific verb (search) and resource (the European Commission's ESCO classification) and states the two entity types covered, occupations or skills. It also spells out the query forms accepted (job title, synonym, skill name) and the language scope, so an agent can distinguish it from a detail-lookup tool for a single ESCO entity.

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: the tool is for resolving a free-text title/synonym/skill to ESCO concepts. There is no explicit when-to-use versus the sibling lookup tools (esco_occupation, esco_skill) or guidance on ambiguity resolution when multiple ranked matches come back.

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