Skip to main content
Glama
othmansamih

MCP Server Example

by othmansamih
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_documentationA
Search for and retrieve documentation from LlamaIndex or LangChain sites.

This tool searches for relevant documentation using Serper API and then scrapes
the content from the top results to provide comprehensive information.

Args:
    query: Search query for documentation (e.g., "vector store", "chat models", "retrieval")
    library: The library to search for ('llamaindex' or 'langchain')
    max_results: Maximum number of documentation pages to retrieve (1-2, default 2)

Returns:
    Formatted documentation content from the search results

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

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with others. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern (get_documentation). Consistency is trivially maintained with one tool.

Tool Count3/5

A single tool feels thin for a server, even if the tool is comprehensive. The server lacks the breadth typical of a well-scoped integration, making it borderline.

Completeness5/5

The tool fully covers its stated domain of retrieving documentation from LlamaIndex or LangChain. It provides appropriate parameters and returns comprehensive content, with no obvious gaps for a read-only documentation tool.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources