metrics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_metricsA | List the metrics this warehouse can answer for. Returns id, label, a one-line definition and the dimensions each may be cut by. Start here: a metric that is not on this list cannot be computed, and the honest answer to a question about it is that it does not exist yet. |
| get_metricB | The full definition of one metric, including its caveats. Read the caveats before describing a number to anyone. They are where the reasons a figure is easy to misread are written down — a denominator that is not what a reader would assume, a most-recent month that is not yet complete. |
| query_metricA | Compute a metric over a range of months, optionally cut by one dimension. Months are 'YYYY-MM' and both ends are inclusive. The reply carries a |
| verify_answerA | Check that every number in Call this on the answer you intend to give, before giving it. If it comes back with unverified numbers, the answer is wrong somewhere: fix it or say less. Do not restate a rejected number with different wording. |
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 4 tools
Each tool has a clearly distinct role: listing available metrics, retrieving full definitions with caveats, computing metric values, and verifying drafted answers. There is no overlap or ambiguity about which tool to call for a given step.
All tool names follow the same snake_case verb_noun pattern: list_metrics, get_metric, query_metric, verify_answer. The pattern is consistent and predictable, with only the expected singular/plural variation for the metric resource.
Four tools is well-scoped for a read-only metrics warehouse surface. Each tool covers a necessary step in the workflow and none feel redundant or missing.
The tool set covers the full analytical workflow: discover what metrics exist, understand their exact definitions and caveats, query them, and verify any final answer before it is delivered. There are no obvious dead ends or missing operations for the stated purpose.