agentic-knowledge
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search for documentation in available docsets. Returns file path, line number, matched content, and surrounding context lines. š AVAILABLE DOCSETS: ā¢ mcp-typescript-sdk (MCP TypeScript SDK) - Official TypeScript SDK for Model Context Protocol ā¢ vitepress-docs (VitePress Documentation) - VitePress static site generator documentation ā¢ local-docs (Local Documentation) - Local documentation: ./docs |
| list_docsetsA | List all available documentation sets (docsets) with detailed information. Note: The search_docs tool already shows available docsets in its description, so this tool is mainly for getting additional metadata. |
| init_docsetA | Initialize a docset by downloading and preparing its content sources. Run this when a docset is configured but not yet initialized. š AVAILABLE DOCSETS TO INITIALIZE: ā¢ mcp-typescript-sdk (MCP TypeScript SDK) ā¢ vitepress-docs (VitePress Documentation) ā¢ local-docs (Local Documentation) |
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 distinct action (search, list, init), but search_docs also lists available docsets, creating a minor overlap with list_docsets. Despite this, the tools are clearly differentiated by their core purposes.
All tool names follow the verb_noun snake_case pattern: search_docs, list_docsets, init_docset. This is consistent and predictable.
Three tools is within the ideal 3-15 range, and each tool serves a necessary function without redundancy. The count is well-scoped for the server's documentation search purpose.
The set covers the complete lifecycle: init_docset for setup, list_docsets for discovery, and search_docs for querying. No obvious gaps exist for the intended use case.