lockwood-group-observability-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INKWELL_PROVIDER | No | Embedding provider: 'stub' (offline) or 'real' (HTTP embeddings). | stub |
| INKWELL_BUDGET_MS | No | Per-call latency budget in milliseconds. | 150.0 |
| INKWELL_LOG_LEVEL | No | Log level: DEBUG/INFO/WARNING/ERROR. | INFO |
| INKWELL_MAX_RECORDS | No | Resource guard: max records per call. | 20000 |
| INKWELL_MAX_CLUSTERS | No | Cluster cap K (bounds per-record cost). | 64 |
| INKWELL_EMBEDDING_DIM | No | Embedding dimension. | 128 |
| INKWELL_EMBED_API_KEY | No | API key for the real embedding provider (used when INKWELL_PROVIDER=real). | |
| INKWELL_EMBED_ENDPOINT | No | HTTP endpoint for the real embedding provider (used when INKWELL_PROVIDER=real). | |
| INKWELL_MAX_MESSAGE_BYTES | No | Resource guard: max bytes per message. | 16384 |
| INKWELL_SIMILARITY_THRESHOLD | No | Cosine threshold for joining a cluster. | 0.55 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| triage_logsA | Cluster a window of log records by semantic similarity and rank the clusters for incident triage. Returns clusters worst-first. |
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 1 tool
With only a single tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clear and unambiguous.
The single tool name 'triage_logs' follows a clear verb_noun pattern in snake_case. Without other tools to compare, there is no inconsistency.
The server is named for observability yet exposes only one tool. A single tool is too few for the apparent breadth of an observability platform, making the count inadequate.
The tool only performs log triage via clustering. Missing are core observability operations such as querying, filtering, retrieving, or alerting, leaving the surface severely incomplete for the domain.