es-error-lens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ES_INDEX_PATTERN | No | The index pattern to search against. Default is logs-* | logs-* |
| ELASTICSEARCH_URL | No | The URL of the Elasticsearch cluster. Default is http://localhost:9200 | http://localhost:9200 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_errorsC | Search for errors in Elasticsearch logs. |
| get_error_patternsA | Detect recurring error patterns by aggregating similar error messages. Groups errors by message and identifies the most common patterns — useful for separating systemic issues from one-off errors. |
| get_error_contextA | Get full context for an error using its trace ID (correlation ID). Retrieves the error and all related logs sharing the same trace ID, providing complete request context for debugging. |
| analyze_error_trendA | Analyze error rate trends over time for a service. Builds a time-series histogram of error counts to identify spikes, patterns, and direction of travel. |
| compare_errorsA | Compare two errors to find similarities and differences. Useful for judging whether two failures are related or share a root cause. |
| health_checkA | Check Elasticsearch connection health. Returns: Dictionary with: - status: "healthy" or "unhealthy" - elasticsearch_url: Configured Elasticsearch URL - cluster_info: Cluster name/version (when healthy) |
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 6 tools
Each tool has a clearly distinct purpose: trend analysis, comparison, context retrieval, pattern detection, health check, and search. No overlapping functionality.
Five tools follow verb_noun pattern (e.g., analyze_error_trend, search_errors); health_check is noun_verb, a minor deviation. Otherwise consistent snake_case.
Six tools is well-scoped for an error analysis server. Each tool contributes a distinct capability without bloat.
Covers error search, trend analysis, pattern detection, context retrieval, comparison, and health check. No obvious gaps for the observation/analysis domain.