OpenTelemetry Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Your Google API key for the Custom Search API | |
| FASTMCP_LOG_LEVEL | No | The log level for FastMCP | ERROR |
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
| Name | Description |
|---|---|
| read_documentationA | Fetch and convert a OpenTelemetry documentation page to markdown format. UsageThis tool retrieves the content of a OpenTelemetry documentation page and converts it to markdown format. For long documents, you can make multiple calls with different start_index values to retrieve the entire content in chunks. URL Requirements
Example URLsOutput FormatThe output is formatted as markdown text with:
Handling Long DocumentsIf the response indicates the document was truncated, you have several options:
Args: ctx: MCP context for logging and error handling url: URL of the OpenTelemetry documentation page to read max_length: Maximum number of characters to return start_index: On return output starting at this character index Returns: Markdown content of the OpenTelemetry documentation |
| search_documentationA | Search OpenTelemetry documentation using Google Custom Search. UsageThis tool searches across OpenTelemetry documentation for pages matching your search phrase. Use it to find relevant documentation when you don't have a specific URL. Search Tips
API LimitsThe search uses Google's Custom Search API which has usage limits:
Result InterpretationEach result includes:
Args: ctx: MCP context for logging and error handling search_phrase: Search phrase to use limit: Maximum number of results to return (will be capped at 10 due to API limitations) Returns: List of search results with URLs, titles, and context snippets |
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 2 tools
The two tools have clearly distinct purposes: 'read_documentation' fetches and converts specific documentation pages to markdown, while 'search_documentation' searches across documentation for relevant pages. There is no overlap in functionality, and an agent can easily differentiate between retrieving known content and discovering unknown content.
Both tools follow a consistent verb_noun pattern with snake_case naming: 'read_documentation' and 'search_documentation'. The verbs ('read' and 'search') are distinct and appropriate for their functions, and the naming scheme is predictable and readable throughout the set.
With only 2 tools, the server feels thin for its purpose of providing OpenTelemetry documentation access. While the tools cover basic retrieval and search, the scope suggests potential for more operations (e.g., listing documentation categories, filtering by version, or handling API interactions), making the count insufficient for a comprehensive documentation server.
The server covers core documentation access with read and search functions, but there are notable gaps. It lacks tools for browsing documentation structure (e.g., listing sections or topics), handling updates or version-specific content, or integrating with other OpenTelemetry resources, which limits agent workflows to basic lookup tasks without broader context.