skosmos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: debug, info, warn, error (written to stderr) | info |
| MCP_HTTP_HOST | No | Bind address for the StreamableHTTP server | 127.0.0.1 |
| MCP_HTTP_PORT | No | TCP port for the StreamableHTTP server | 3000 |
| SKOSMOS_TIMEOUT | No | HTTP request timeout in milliseconds | 30000 |
| SKOSMOS_BASE_URL | Yes | Base URL of the Skosmos instance | |
| SKOSMOS_CACHE_TTL | No | Cache entry TTL in seconds | 300 |
| SKOSMOS_USER_AGENT | No | User-Agent header sent with API requests | skosmos-mcp/0.1.0 |
| SKOSMOS_DEFAULT_LANGUAGE | No | Default language code for labels | en |
| SKOSMOS_DEFAULT_VOCABULARY | No | Default vocabulary id when not specified in a tool call | |
| SKOSMOS_MAX_TRAVERSAL_DEPTH | No | Hard cap on BFS traversal depth | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vocabulariesC | List all available vocabularies in the Skosmos instance |
| get_vocabularyC | Get details of a specific vocabulary including top concepts |
| get_conceptC | Get full concept details including broader, narrower, and related concepts |
| get_concept_labelB | Get all labels (prefLabel, altLabel, hiddenLabel) for a concept URI |
| concept_pathA | Get the hierarchy path from a concept to its root via broader transitive relations |
| search_conceptsA | Full-text search for concepts across one or all vocabularies |
| autocompleteB | Autocomplete concept labels by prefix |
| resolve_labelC | Resolve a label text to concepts in a vocabulary |
| labelsA | Get all labels for a concept URI in a vocabulary |
| broader_conceptsA | BFS traversal of broader (parent) concepts up to a specified depth |
| narrower_conceptsB | BFS traversal of narrower (child) concepts down to a specified depth |
| related_conceptsB | BFS traversal of related concepts up to a specified depth |
| traverse_conceptsB | BFS traversal using a mix of broader, narrower, and/or related relationships |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vocabularies |
TDQS
Scored across 13 tools
Most tools have distinct purposes, but 'get_concept_label' and 'labels' overlap significantly, both retrieving labels for a concept URI. Additionally, 'broader_concepts' and 'traverse_concepts' can be confused since traverse supports broader traversal. This creates some ambiguity for an agent.
Tool names mostly follow a consistent verb_noun pattern (e.g., list_vocabularies, get_concept, resolve_label). However, 'autocomplete' is a single word and 'concept_path' is noun_noun, breaking the pattern. The overall structure is clear despite these minor deviations.
With 13 tools, the server is well-scoped for SKOS vocabulary browsing. It covers listing, searching, detail retrieval, and hierarchy traversal without being overwhelming. The count is appropriate for its purpose.
The tool surface covers core SKOS operations: vocabulary listing, concept details, labels, hierarchy traversal (broader, narrower, related), and search (autocomplete, full-text, label resolution). Missing are concept creation/modification (likely out of scope) and some non-core features like concept collections, but the browsing workflow is complete.