Skip to main content
Glama
mcp-server

mcp-server

by yasabbasi

metrics_quality_report

Read-only

Inspect a pipeline run’s data quality status, ingested and quarantined row counts, and failed checks before trusting metrics from runs that did not pass.

Instructions

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.

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_quality_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
run_idYes
statusYes
tablesYes
more_failedYes
failed_checksYes
passed_checksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 safety is covered. The description adds genuinely useful behavior beyond that: a hard cap of 50 failed checks, a `more_failed` counter for truncation, and a `passed_checks` count — the kind of truncation disclosure an agent needs to avoid misreading results.

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

Conciseness3/5

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

Everything present is relevant, and the most important guidance (when to trust the numbers) is placed last where it may be skimmed past. The opening sentence is a long enumerated run-on listing return fields that the output schema already documents, which inflates length without adding much.

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 tool with an output schema, the description covers what an agent needs: what the report contains, how results are truncated, and when the report should gate trust in other metrics. Nothing material is missing.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on inputs.

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?

The description states specifically what the tool reports: the run's `status`, per-table `rows_ingested`/`rows_quarantined`, and non-passing checks with their fields. It implicitly distinguishes itself from `metrics_freshness` by naming that sibling as the source of `quality_status`. It lacks an explicit verb ('returns the quality report for...'), which keeps it just short of a 5.

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?

It gives a clear triggering condition: 'Look here before trusting a number from a run whose status is not `pass`', and routes the agent to `metrics_freshness` for obtaining that status. There is no explicit when-not guidance or mention of the other siblings, but the primary use case is unambiguous.

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