Oli Docs MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_docsD | – |
| searchD | – |
| get_sectionD | – |
| citeD | – |
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 has a clearly distinct purpose: listing docs, searching, retrieving a specific section, and generating citations. No overlap or ambiguity.
Tool names are lowercase with underscores, but the pattern is inconsistent: 'list_docs' and 'get_section' follow verb_noun, while 'search' and 'cite' are bare verbs without an explicit object. Still readable but less predictable.
Four tools is a well-scoped set for a documentation server, covering browsing, searching, section retrieval, and citation without unnecessary bloat.
The core documentation workflow (list, search, get, cite) is covered. A minor gap is the lack of a 'get_doc' tool for retrieving full documents, but section-level access likely suffices for most use cases.