@pooml/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POOML_URL | Yes | The base URL of your pooml instance. | |
| POOML_QUERY_AUTH_SECRET | Yes | The query API auth secret, at least 32 characters long. | |
| POOML_CF_ACCESS_CLIENT_ID | No | Cloudflare Access service token client ID (required if the pooml server is behind Cloudflare Tunnel with Access). | |
| POOML_CF_ACCESS_CLIENT_SECRET | No | Cloudflare Access service token client secret (required if the pooml server is behind Cloudflare Tunnel with Access). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_logsA | Run a read-only SQL (SQLite dialect) query over the logs of this pooml instance. Table logs(id, timestamp, ingested_at, level, service, host, message, parsed, raw):
|
| query_metricsA | Run a read-only SQL (SQLite dialect) query over the metrics of this pooml instance. Table metrics(id, timestamp, name, type, value, service, host, labels):
|
| list_metricsA | List the metrics this pooml instance has: name, type (counter/gauge), service, datapoint count, last-seen timestamp (ms). Call this before query_metrics when unsure of metric names. |
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 3 tools
Each tool targets a clearly distinct function: query_logs handles log data, query_metrics handles metric data, and list_metrics provides metadata discovery for metrics. There is no meaningful overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern: query_logs, list_metrics, and query_metrics. The use of 'list' for discovery and 'query' for SQL access is a clear and predictable convention.
Three tools is well-scoped for a read-only observability server: one for logs, one for metric metadata, and one for metric data. Each tool provides substantial functionality, so the count feels appropriate rather than thin.
The tool surface covers the stated domain completely: log querying, metric listing, and metric querying are all present with rich SQL capabilities. No obvious gap exists for the read-only observability purpose this server appears to serve.