OLS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_termsC | Search for terms across ontologies using the OLS search API. |
| get_ontology_infoC | Get detailed information about a specific ontology. |
| search_ontologiesC | Search for available ontologies. |
| get_term_infoC | Get detailed information about a specific term. |
| get_term_childrenB | Get direct children of a specific term. Args: term_iri: The IRI of the term ontology: The ontology identifier include_obsolete: Include obsolete entities size: Maximum number of results Returns: JSON formatted list of child terms |
| get_term_ancestorsC | Get ancestor terms (parents) of a specific term. Args: term_iri: The IRI of the term ontology: The ontology identifier include_obsolete: Include obsolete entities size: Maximum number of results Returns: JSON formatted list of ancestor terms |
| find_similar_termsC | Find terms similar to the given term using LLM embeddings. Args: term_iri: The IRI of the reference term ontology: The ontology identifier size: Maximum number of similar terms to return Returns: JSON formatted list of similar terms |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no ambiguity: find_similar_terms uses embeddings for similarity, get_ontology_info and get_term_info retrieve metadata, get_term_ancestors and get_term_children handle hierarchical relationships, and search_ontologies and search_terms perform different types of searches. The descriptions clearly differentiate their functions.
All tools follow a consistent verb_noun pattern with snake_case: find_similar_terms, get_ontology_info, get_term_ancestors, get_term_children, get_term_info, search_ontologies, and search_terms. The naming is predictable and readable throughout the set.
With 7 tools, this is well-scoped for an ontology server, covering core operations like searching, retrieving metadata, and exploring term hierarchies. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides strong coverage for ontology exploration, including search, metadata retrieval, and hierarchical navigation. A minor gap is the lack of update or management tools (e.g., create_term, update_ontology), but this is reasonable for a read-focused server, and agents can work effectively with the provided tools.