Skip to main content
Glama
mcp-server

mcp-server

by yasabbasi

metrics_freshness

Read-only

Check the pipeline run, source, covered dates, publish time, and quality status behind metrics to assess data freshness and identify rows that may still change.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "metrics_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
run_idYes
sourceYes
generated_atYes
data_max_dateYes
data_min_dateYes
restated_fromYes
quality_statusYes
contract_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: generated_at is UTC, and rows dated on or after restated_from may change on later runs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the returned provenance and date range, followed by the usage reason and the restatement caveat. No filler or unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only metadata tool with an output schema, the description supplies the key context: what provenance and date fields are reported, why to call it, and the restated_from caveat. Field-level details can be carried by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. No additional parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States clearly that the tool reports pipeline-run provenance, data date range, generated_at UTC, and quality status, and that it is used to learn coverage and freshness. It is specific about the resource, but does not explicitly differentiate itself from sibling tools such as metrics_quality_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call it to learn what dates the data covers and how fresh it is, giving a clear usage condition. It does not state when not to use it or name an alternative sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.