Skip to main content
Glama
sagacious-satadru

Documentation MCP Server

by sagacious-satadru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_docsA
Search the docs for a given query and library.
Supports langchain, llama-index, and openai.

Args:
    query: The query to search for (e.g.: "Chroma DB").
    library: The library to search in. One of langchain, llama-index, openai.
    max_chars: Maximum characters to return (default: 1000 for free tier).

Returns:
    Text from the documentation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_docs' has a clearly defined and distinct purpose of searching documentation for specified libraries.

Naming Consistency5/5

With only one tool, naming consistency is inherently perfect. The tool name 'get_docs' follows a clear verb_noun pattern that would be consistent if more tools were added.

Tool Count2/5

A single tool for a documentation server feels insufficient for the apparent scope. While the tool covers search functionality, typical documentation servers would benefit from additional tools like list_libraries, get_document, or browse_topics to provide more complete coverage.

Completeness2/5

The tool surface is severely incomplete for a documentation server. While search functionality is provided, there are significant gaps: no way to list available libraries, browse documentation structure, get specific documents by reference, or access metadata about documentation resources. This will likely cause agent failures when trying to comprehensively work with documentation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources