Schema | Tempo MCP Server

Tempo MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
tempo_search_tracesA	Search traces using TraceQL query language. Automatically handles various query syntax formats. The query parser will normalize your query to work with Tempo. Default time range: last 7 days.
tempo_get_traceB	Get complete trace data by trace ID, including all spans with full details
tempo_get_trace_spansB	Get all spans from a specific trace with optional filtering by service name, span name, duration, attributes, or error status
tempo_search_spansC	Search for traces and return all matching spans across multiple traces with filtering. Useful for finding specific operations across your system.
tempo_get_span_statisticsB	Get aggregated statistics for spans grouped by service, operation, or status. Returns count, avg/min/max/percentile durations.
tempo_query_by_tagB	Convenience method to query traces by specific tag/attribute filters. Useful for filtering by sometag, user.id, environment, etc.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UjjwalSk/tempo-mcp-server'

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