sinequa-docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host the HTTP server listens on. Equivalent to the `--host` option. | 127.0.0.1 |
| PORT | No | Port for the HTTP server (only used with HTTP mode). Equivalent to the `--port` option. | 5181 |
| DOCS_LIBRARIES | No | Libraries to serve, as `name=URL` pairs separated by commas (defaults to atomic, atomic-angular, galactik on hebus.github.io). Equivalent to the `--libraries` option. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_searchA | Full-text search in the published documentation of atomic (https://hebus.github.io/atomic-docs/docs/), atomic-angular (https://hebus.github.io/atomic-angular-docs/docs/atomic-angular/), galactik (https://hebus.github.io/atomic-angular-docs/docs/galactik/). Returns the best sections (two per page at most) with their URL and path; read one with docs_read. |
| docs_readA | A documentation page as Markdown, from its path or URL (as returned by docs_search or docs_index). A '#anchor' or 'section' returns that section only. |
| docs_indexA | Table of contents of atomic (https://hebus.github.io/atomic-docs/docs/), atomic-angular (https://hebus.github.io/atomic-angular-docs/docs/atomic-angular/), galactik (https://hebus.github.io/atomic-angular-docs/docs/galactik/): title, path and one-line description of each page. |
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 3 tools
Each tool targets a clearly distinct operation on the documentation: docs_search finds sections, docs_read retrieves a specific page/section, and docs_index returns the table of contents. There is no meaningful overlap, and the descriptions explicitly clarify how search/read/index relate.
All three tools use the same docs_ prefix followed by a precise verb/noun (search, read, index), giving a fully predictable pattern. The convention is uniform across the entire set.
Three tools is well-scoped for a documentation server: one discovery mechanism (index), one query mechanism (search), and one retrieval mechanism (read). Each tool earns its place with no redundancy.
The set covers the full documentation-reading lifecycle: browsing the table of contents, searching full text, and reading pages or specific sections as Markdown. No obvious gaps or dead ends exist for this domain.