Skip to main content
Glama

SourceGeek

Get ESCO skill

esco_skill
Read-only

Fetch an ESCO skill or knowledge concept by URI: description, skill type, reuse level, broader and narrower skills, and the occupations for which it is essential or optional.

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_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesESCO skill URI, e.g. http://data.europa.eu/esco/skill/<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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the response shape (description, skill type, reuse level, broader/narrower, essential/optional occupations), but says nothing about invalid-URI behavior or truncation semantics beyond what the schema states.

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 front-loaded sentence that states the lookup key first and then the payload, with no filler or repetition of schema details.

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?

With no output schema, the description usefully enumerates the fields returned, which is the main thing an agent needs in order to decide whether to call it. Only error behavior and the meaning of 'essential' vs 'optional' occupations are left unstated.

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 the URI pattern, limit range and language enum all documented in the schema. The description adds only the framing that the URI identifies a skill or knowledge concept; it contributes no extra syntax, format or defaulting detail, so the 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 a specific verb and resource ('Fetch an ESCO skill or knowledge concept by URI') and enumerates the returned fields, which lets an agent distinguish a URI-keyed lookup from the keyword-based sibling esco_search. It stops short of naming any sibling explicitly, so it lands just below the top mark.

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 by the 'by URI' framing: call this when you already hold an ESCO skill URI. There is no explicit when-to-use/when-not guidance and no pointer to esco_search for the case where the agent only has a name rather than a URI.

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