Skip to main content
Glama
mcp-server

mcp-server

by yasabbasi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATA_OUTPUT_DIRYesThe 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
metrics_breakdownA

One metric split by by, category or distribution_center, over start to end (ISO dates, both included). slices holds each slice's name and value, largest first; at most 50 are returned, and truncated says whether there were more. Counts and money are summed over the days, and aov, return_rate and conversion_rate are recomputed from the slice's summed parts; a ratio is null when its denominator is 0. Ratios are fractions between 0 and 1, rounded to four places. orders, product_view_sessions and converted_sessions are distinct within the slice, and they and every ratio must not be summed across slices; a slice's aov is revenue per order in that slice. adds_up says whether the slices add up to the total, true only for revenue, units and returned_units. approximate is true for the session metrics over more than one day, because a session that crosses midnight is counted on both days. On contract v1 outputs only revenue, units, returned_units and return_rate can be split; call metrics_daily_totals for the others. includes_provisional is true when the range reaches restated_from, so the numbers may still change. Call metrics_freshness for the dates the data covers and the contract version.

metrics_daily_totalsA

The published totals from start to end (ISO dates, both included) by grain: day, week (starting Monday) or month. It returns columns: dates holds the first day of each period that falls in the range, and values holds one list per metric, lined up with dates. metrics picks the metrics; leave it out for all of them. At week and month, counts and money are summed and aov, return_rate and conversion_rate are recomputed from the summed parts; a ratio is null when its denominator is 0. Ratios are fractions between 0 and 1, rounded to four places. The session metrics, named in approximate, are approximate above day, because a session that crosses midnight is counted on both days. A period is provisional when any of its days is on or after restated_from, so its numbers may still change. Call metrics_freshness for the dates the data covers and metrics_list for the metric names.

metrics_explainA

The full definition of one metric: its name, display label, unit (usd, count or ratio), whether it is additive, a plain-language description, its aggregation (sum, count, count_distinct or ratio) and its formula. Ratios are fractions between 0 and 1, rounded to four places. Call it before explaining what a number means. Call metrics_list for the valid names.

metrics_freshnessA

Which pipeline run the metrics come from: its id, source, contract version, data range (data_min_date to data_max_date), publish time (generated_at, UTC) and quality status. Call it to learn what dates the data covers and how fresh it is. Rows dated on or after restated_from may still change on later runs.

metrics_listA

Every published metric in contract order: its name, display label, unit (usd, count or ratio) and whether it is additive. A metric is additive when summing it across categories and distribution centers gives the total. orders, the session counts and every ratio are not additive, because one order or session can span several slices. Ratios are fractions between 0 and 1, rounded to four places. Call metrics_explain for one metric's full definition.

metrics_quality_reportA

What the pipeline checked on the run the metrics come from: the run's status (pass, warn or fail), the rows_ingested and rows_quarantined of each source table in tables, and the checks that did not pass in failed_checks, each with its name, table, severity, status and message. At most 50 are returned: more_failed counts the ones left out, and passed_checks counts the checks that passed. Look here before trusting a number from a run whose status is not pass; metrics_freshness gives that status as quality_status.

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 6 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues