dbtBigQuery

health_check

Check if the semantic layer can serve queries by verifying manifests, MetricFlow availability, and warehouse credentials. Run this first to diagnose environmental query failures.

Instructions

Report whether the semantic layer is ready to serve queries: manifests
present, MetricFlow available, warehouse credentials configured.

Call this first if a query fails for reasons that look environmental.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses what the tool checks and frames the output as a readiness report. It stops short of explicitly stating whether it performs external calls or whether it is side-effect-free, but the stated checks give sufficient behavioral context for a health-check tool.

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?

Two sentences with no filler. The purpose and checks are front-loaded, and the usage guidance follows immediately. Every sentence earns its place.

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?

With zero parameters and an output schema present, the description provides everything an agent needs to decide when to call it and what it will report. No inputs, preconditions, or side-effect warnings are 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 has zero parameters and schema coverage is 100%, so there is no parameter semantics for the description to add. Per the baseline for zero-parameter tools, this is fully adequate.

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

Purpose5/5

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

The description states a specific verb and resource: 'Report whether the semantic layer is ready to serve queries,' and enumerates concrete readiness checks (manifests present, MetricFlow available, warehouse credentials configured). This clearly distinguishes health_check from the sibling metric-querying tools.

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

Usage Guidelines5/5

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

It provides an explicit invocation condition: 'Call this first if a query fails for reasons that look environmental.' This is a clear, actionable decision rule. The sibling tools are for metric operations and are not realistic alternatives for a health check, so no exclusion guidance is needed.

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

Deploy Server