mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_OUTPUT_DIR | Yes | The full path of the output directory containing the published outputs (e.g. parquet/<table>.parquet). There is no default directory: if the variable is unset or a file is missing, the tool says what to set. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| metrics_breakdownA | One metric split by |
| metrics_daily_totalsA | The published totals from |
| metrics_explainA | The full definition of one metric: its |
| metrics_freshnessA | Which pipeline run the metrics come from: its id, source, contract version, data range ( |
| metrics_listA | Every published metric in contract order: its |
| metrics_quality_reportA | What the pipeline checked on the run the metrics come from: the run's |
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 targets a clearly different need: slice-by-dimension (breakdown), time series (daily_totals), metadata (list/explain), and pipeline trust (freshness/quality_report). The only mild overlap is between metrics_freshness and metrics_quality_report, since freshness surfaces quality_status and points to the report, but the split between run identity/date coverage and check-level detail is explained well.
All six tools share the metrics_ namespace prefix and snake_case suffixes, giving a strongly predictable pattern. The suffixes mix verbs (explain, list) with nouns (breakdown, daily_totals, quality_report, freshness), which is a minor deviation but still very readable.
Six tools is well-scoped for a metrics query server: discovery (list, explain), retrieval (daily_totals, breakdown), and trust (freshness, quality_report) each get dedicated tools with no filler. Nothing looks redundant or missing at the count level.
The surface covers the full query lifecycle—discover metrics, understand definitions, pull totals and breakdowns across grains, and verify data currency and quality—with no obvious dead ends. The main gap is there is no way to enumerate valid `by` dimensions or category/distribution-center values, so an agent must discover them by trial or from breakdown results.