mcp-ubergraph-query
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging verbosity | INFO |
| QUERY_LIMIT_MAX | No | Maximum allowed LIMIT value | 1000 |
| CACHE_TTL_SECONDS | No | Cache entry lifetime | 3600 |
| ENABLE_QUERY_CACHE | No | Enable in-memory LRU result cache | true |
| UBERGRAPH_ENDPOINT | No | SPARQL endpoint URL | https://ubergraph.apps.renci.org/sparql |
| QUERY_TIMEOUT_DEFAULT | No | Default query timeout (seconds) | 30 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_ubergraphA | Execute a SPARQL query against the Ubergraph endpoint. Use for custom queries when other tools don't fit your needs. |
| get_term_infoA | Get comprehensive information about a specific ontology term (labels, definitions, synonyms, types). |
| search_termsB | Search for ontology terms by label or synonym. Returns matching terms with their IDs. |
| get_hierarchyB | Get hierarchical relationships for a term (parents, children, ancestors, descendants). |
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 4 tools
Each tool serves a clearly distinct purpose: searching terms, retrieving term details, getting hierarchy, and executing custom SPARQL queries. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_hierarchy, get_term_info, query_ubergraph, search_terms), making them predictable and easy to understand.
With 4 tools, the server is well-scoped for ontology querying. Each tool is essential and covers the primary use cases without being too few or excessive.
The tool set covers the core needs: search, term retrieval, hierarchy, and custom queries. Minimal gaps exist, such as batch operations or ontology-wide listings, but the surface is sufficient for most tasks.