Skip to main content
Glama

get_docs

Search documentation for langchain, openai, and llama-index libraries to find specific information using targeted queries.

Instructions

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
libraryYes

Implementation Reference

  • main.py:48-72 (handler)
    The core handler function for the 'get_docs' MCP tool. Registered via @mcp.tool() decorator. Performs site-specific Google search using Serper API and aggregates text content from top results.
    @mcp.tool()  
    async def get_docs(query: str, library: str):
      """
      Search the latest docs for a given query and library.
      Supports langchain, openai, and llama-index.
    
      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
      """
      if library not in docs_urls:
        raise ValueError(f"Library {library} not supported by this tool")
      
      query = f"site:{docs_urls[library]} {query}"
      results = await search_web(query)
      if len(results["organic"]) == 0:
        return "No results found"
      
      text = ""
      for result in results["organic"]:
        text += await fetch_url(result["link"])
      return text
  • main.py:20-37 (helper)
    Helper function to perform web search using the Serper API, returning search results.
    async def search_web(query: str) -> dict | None:
        payload = json.dumps({"q": query, "num": 2})
    
        headers = {
            "X-API-KEY": os.getenv("SERPER_API_KEY"),
            "Content-Type": "application/json",
        }
    
        async with httpx.AsyncClient() as client:
            try:
                response = await client.post(
                    SERPER_URL, headers=headers, data=payload, timeout=30.0
                )
                response.raise_for_status()
                return response.json()
            except httpx.TimeoutException:
                return {"organic": []}
  • main.py:38-47 (helper)
    Helper function to fetch content from a URL and extract plain text using BeautifulSoup.
    async def fetch_url(url: str):
      async with httpx.AsyncClient() as client:
            try:
                response = await client.get(url, timeout=30.0)
                soup = BeautifulSoup(response.text, "html.parser")
                text = soup.get_text()
                return text
            except httpx.TimeoutException:
                return "Timeout error"
  • main.py:14-18 (helper)
    Configuration dictionary mapping supported library names to their documentation site URLs, used for site-specific searches.
    docs_urls = {
        "langchain": "python.langchain.com/docs",
        "llama-index": "docs.llamaindex.ai/en/stable",
        "openai": "platform.openai.com/docs",
    }
  • main.py:49-60 (schema)
    Type hints and docstring defining the input schema (query: str, library: str ∈ ['langchain','llama-index','openai']) and output (str: text from docs).
    async def get_docs(query: str, library: str):
      """
      Search the latest docs for a given query and library.
      Supports langchain, openai, and llama-index.
    
      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
      """
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'latest docs' and 'search,' but fails to describe critical behaviors such as authentication needs, rate limits, pagination, error handling, or what 'latest' means (e.g., versioning or update frequency). This leaves significant gaps for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, with the core purpose stated first, followed by supported libraries and parameter details in a structured 'Args' and 'Returns' format. It avoids redundancy, but the 'Returns' section is vague ('Text from the docs'), slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose, parameters, and return type broadly, but lacks details on behavioral aspects like search scope, result format, or error conditions, leaving room for improvement in guiding an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'query' is for searching (e.g., 'Chroma DB') and 'library' specifies the target (e.g., 'langchain'), including examples and listing supported libraries. This compensates well for the schema's lack of descriptions, though it could detail format constraints (e.g., case sensitivity).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Search the latest docs for a given query and library.' It specifies the verb ('search'), resource ('docs'), and scope ('latest docs for a given query and library'). However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage context by listing supported libraries ('langchain, openai, and llama-index'), which suggests when to use this tool. However, it lacks explicit guidance on when not to use it or alternatives, and does not mention prerequisites or constraints beyond the library options.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alejandro-ao/mcp-server-example'

If you have feedback or need assistance with the MCP directory API, please join our Discord server