MCP server for ontoloom ontology tools - A structured toolkit for building and exploring OWL 2 ontologies backed by SQLite
Ontoloom demonstrates solid definition quality with consistent naming patterns, comprehensive parameter descriptions, and explicit tool annotations. All 19 tools follow verb_noun conventions (create_, add_, remove_, find_, get_, describe_, export_, list_, read_, match_, set_, annotate_, replace_, rename_). Input schemas are present and typed for all tools. However, tool descriptions are brief (avg ~60 chars, below the 194-char baseline), and output schemas are not documented in the visible code. Error handling guidance is minimal, tools lack recovery hints and actionable error messages. The server uses fastmcp's Tool.from_function pattern, which infers schemas from function signatures; while this ensures consistency, it means schemas are not explicitly visible in the source, creating a verification gap.
Add OWL 2 axioms to an ontology
Add or remove annotations on an axiom
Create a new empty ontology database
Create a named set of axiom hashes or entity IRIs that persists across calls
Get summary statistics about an ontology
Export ontology axioms and entities to JSONL format
Find axioms matching constraints
Find annotation values shared by more than one entity
Tool descriptions are uniformly brief (avg ~60 chars vs. 194-char baseline). Descriptions lack context on WHEN to use each tool, prerequisites, or dependencies. E.g., 'Add OWL 2 axioms to an ontology' does not explain when to call add_axioms vs. replace_axiom, or that axioms must be valid OWL 2 EL syntax.
Output schemas are not documented. The server uses fastmcp's Tool.from_function, which infers schemas from function signatures, but return types are not visible in the provided source. LLMs cannot plan downstream calls or extract required fields (e.g., axiom_hash from add_axioms response) without documented output structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Find entities matching search criteria
Get detailed information about an entity
List all named selections in an ontology
Find axioms matching a pattern
Read the contents of a named selection
Remove axioms from an ontology by hash or selection
Remove a namespace prefix definition
Delete named selections
Replace an IRI with a new one throughout the ontology or within a selection
Atomically replace an axiom with a new one, carrying forward annotations
Define or update a namespace prefix
Destructive operations (remove_axioms, rename_iri, remove_selections) require a 'confirm' token but lack clear error guidance. If a confirmation token is rejected (e.g., selection changed), the error message should explain why and how to recover. Current implementation likely returns a generic error.
Parameter descriptions lack format/constraint details. E.g., 'axioms' in add_axioms is described as 'List of axioms to add' but does not specify the axiom object structure, required fields, or valid OWL 2 types. 'pattern' in match_axioms is similarly vague.
No pagination or result-limiting guidance. Tools like find_entities, find_axioms, and find_duplicate_entities may return large result sets. Descriptions do not mention limits, pagination parameters, or token cost implications for LLM context.