Skip to main content
Glama

SourceGeek

Get ESCO occupation

esco_occupation
Read-only

Fetch an ESCO occupation by URI: description, ESCO/ISCO codes, alternative job titles, broader and narrower occupations, and the essential and optional skills/knowledge the EU taxonomy lists for it.

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": {
      "uri": "<uri>"
    },
    "name": "esco_occupation"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesESCO occupation URI, e.g. http://data.europa.eu/esco/occupation/<uuid>.
limitNoMaximum items returned per related list (1-200, default 50). Each list also reports its full total.
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

A4/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful context about what the response contains, though it does not discuss error behavior, return formatting, or pagination beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence that front-loads the action and then lists the relevant returned fields. It is dense but not wasteful.

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 fetch tool with no output schema, the description gives enough detail about the returned occupation data. It is only slightly incomplete in not explaining how to obtain the URI or how related lists are paginated.

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%, so the URI, limit, and language parameters are already well documented in the schema. The description reinforces URI-based fetching but adds no extra parameter meaning beyond what the schema provides.

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 verb and resource: fetch an ESCO occupation by URI. It also enumerates the returned content, including codes, titles, broader/narrower occupations, and skills, making it clearly distinct from a search tool.

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?

The URI-based invocation implies this is a lookup step, likely after searching, but the description does not explicitly say when to use this instead of esco_search or esco_skill. Usage is inferable but not spelled out.

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