knowflow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JENKINS_URL | No | URL of the Jenkins server. Required only if connecting to live Jenkins pipeline. | |
| JENKINS_TOKEN | No | API token for Jenkins authentication. Required only if connecting to live Jenkins pipeline. | |
| BIGQUERY_PROJECT_ID | No | Your Google Cloud project ID for BigQuery GA4 export. Required only if connecting to live GA4 data. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Semantic search across the documentation corpus. Returns ranked topics with relevance scores and excerpts. |
| get_topicA | Retrieve full Markdown content of a topic by ID. |
| list_topicsC | Browse the full corpus index with optional filters. |
| get_content_gapsA | Surface search queries that returned zero or low results — documentation your users need but doesn't exist yet. |
| get_build_statusC | Check Jenkins CI/CD publish pipeline status. |
| evaluate_pipelineA | Run RAGAS-style evaluation on the RAG pipeline. Measures answer relevance, faithfulness, and context recall across a test query set. |
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 6 tools
Each tool has a clearly distinct purpose: evaluating pipelines, checking build status, finding content gaps, retrieving topics, listing topics, and searching docs. No overlap in functionality.
All tools follow a consistent verb_noun pattern in snake_case (e.g., evaluate_pipeline, get_build_status, search_docs), making the set predictable and easy to navigate.
With 6 tools, the server is well-scoped for its purpose of documentation knowledge management and pipeline evaluation. The count is neither too sparse nor overwhelming.
The server provides read and analysis capabilities (list, get, search, evaluate) but lacks tools for creating, updating, or deleting topics, which are notable gaps for a documentation system.