Skip to main content
Glama
ThainaJardim

observability-mcp

by ThainaJardim

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
query_loki_logsA

Run a Loki range query through Grafana datasource proxy.

Args: query: LogQL expression, e.g. {app="myservice"} |= "error". limit: Maximum number of log lines to return (1–5000, default 100). direction: "backward" (newest first, default) or "forward". start: Start of the time range. RFC 3339 or Unix nanosecond string. end: End of the time range. RFC 3339 or Unix nanosecond string.

Returns: JSON payload from Loki with streams and log entries.

query_loki_instantA

Run a Loki instant query through Grafana datasource proxy.

Args: query: LogQL expression. limit: Maximum number of log lines to return (1–5000, default 100). at: Evaluation timestamp. RFC 3339 or Unix nanosecond string. Defaults to now when omitted.

Returns: JSON payload from Loki with matching log entries.

list_loki_labelsA

List available Loki label names from the configured datasource.

Args: start: Optional start of the time range for filtering. end: Optional end of the time range for filtering.

Returns: JSON array of label name strings.

list_loki_label_valuesA

List available values for a given Loki label.

Args: label: Label name, e.g. "app" or "namespace". start: Optional start of the time range for filtering. end: Optional end of the time range for filtering.

Returns: JSON array of label value strings.

query_metricsA

Run an instant PromQL query against Thanos.

Args: query: PromQL expression, e.g. rate(http_requests_total[5m]). time: Optional evaluation timestamp. Accepts RFC 3339 strings (2024-01-01T00:00:00Z) or Unix timestamps as strings. Defaults to now when omitted.

Returns: JSON payload from Thanos containing resultType and result.

query_metrics_rangeA

Run a PromQL range query against Thanos.

Args: query: PromQL expression. start: Start of the time range. RFC 3339 or Unix timestamp string. end: End of the time range. RFC 3339 or Unix timestamp string. step: Query resolution step width. Duration string (60s, 5m) or float seconds.

Returns: JSON payload with resultType: "matrix" and the time-series data.

list_labelsA

List all metric label names available in Thanos.

Args: start: Optional start of the time range for label filtering. end: Optional end of the time range for label filtering.

Returns: JSON array of label name strings.

list_seriesA

List time-series matching a PromQL selector.

Args: match: One or more comma-separated series selectors, e.g. {job="prometheus"} or up,{job="api"}. Each comma-separated value is sent as a separate match[] parameter. start: Optional start timestamp for the look-up window. end: Optional end timestamp for the look-up window.

Returns: JSON array of label-set objects describing each matching series.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct operation and data source (Loki vs. Thanos), with clear naming and descriptions that prevent confusion. Even similar tasks like label listing are differentiated by the datasource prefix.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case, e.g., 'query_loki_instant', 'list_labels'. The naming clearly indicates the action and the target, making it predictable and easy to understand.

Tool Count5/5

With 8 tools covering essential operations for two datasources (metrics and logs), the count is well-scoped. There are no redundant tools, and each tool serves a clear purpose without overwhelming the agent.

Completeness5/5

The tool set covers the core query and metadata exploration for both Loki and Thanos, including instant/range queries, label discovery, and series listing. No obvious gaps exist for standard observability workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues