Skip to main content
Glama
vikramdse

Library Docs MCP Server

by vikramdse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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_docsC
Search the docs for a given query and library.
Supports langchain, llama-index, mcp, and openai.

Args:
    query: The query to search for (e.g. "Chroma DB")
    library: The library to search in (e.g. "langchain")

Returns:
    Text from the docs

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

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clear purpose: searching documentation for specific libraries.

Naming Consistency5/5

The single tool name 'get_docs' follows a clear verb_noun pattern, making it predictable and readable. There are no other tools to compare against, so consistency is inherently perfect.

Tool Count2/5

A single tool for a documentation search server feels too thin for the apparent scope, which involves multiple libraries (langchain, llama-index, mcp, openai). This minimal set may limit functionality and force agents to rely heavily on this one tool for all tasks.

Completeness2/5

The tool surface is severely incomplete for a documentation server. While it supports search, there are obvious gaps such as listing available libraries, browsing documentation sections, or getting metadata about docs. This will likely cause agent failures when more nuanced interactions are needed.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources