actian-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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Semantic search across Actian documentation. Returns the top matching sections with product, version, and topic-type metadata. Use this to answer questions about Actian products. |
| get_topicA | Retrieve the full Markdown content of a specific documentation topic by its ID. Use search_docs first to find the topic_id, then call this to read the full content. |
| list_topicsA | List all available documentation topics, optionally filtered by product or topic type. |
| get_content_gapsA | Returns search queries from the analytics data that returned zero or low results — i.e. topics that users searched for but documentation does not cover. Use this to identify missing documentation. |
| get_build_statusA | Returns the current status of the documentation CI/CD build pipeline in Jenkins, including the last build result, timestamp, and duration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Upgrading Analytics Engine using RPM packages | analytics-engine · 8.0 · task |
| Analytics Engine Spark Connector — overview | analytics-engine · 8.0 · concept |
| Setting up the Tableau connector for Analytics Engine | analytics-engine · 8.0 · task |
| JDBC driver reference — Analytics Engine | analytics-engine · 8.0 · reference |
| Troubleshooting Analytics Engine connection errors | analytics-engine · 8.0 · troubleshooting |
| Backing up and restoring Ingres databases | ingres · 11.x · task |
| Ingres SQL data types reference | ingres · 11.x · reference |
| Configuring an ODBC DSN on Windows — Actian Client | actian-client · 4.2 · task |
| Product rename — Actian Vector to Actian Analytics Engine | analytics-engine · 8.0 · concept |
| Performance tuning — columnar query optimisation | analytics-engine · 8.0 · concept |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: semantic search, content retrieval by ID, listing metadata, analytics for gaps, and build pipeline status. There is no overlap or ambiguity between them.
All tool names consistently follow the verb_noun pattern in snake_case (search_docs, get_topic, list_topics, get_content_gaps, get_build_status). The naming is uniform and predictable.
Five tools is a well-scoped set for a documentation server, covering search, retrieval, listing, analytics, and CI/CD status without unnecessary bloat. Each tool earns its place.
The core documentation workflow is covered: discover topics via search/list, retrieve full content, and identify gaps. The build status tool provides complementary operational visibility, making the surface complete for its purpose.