jawz

Get data health

get_data_health

Read-only

Freshness status for every data source Jawz reads: per-source release date, latest observation date, expected cadence, age in days, and whether any source is stale or unavailable. Also reports whether the ingestion pipeline is keeping up, and carries plain-language notices when a scheduled update has not arrived. Applies when the reliability of a figure depends on how current its underlying data is.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	No
`crons`	No
`notices`	No
`sources`	No
`any_stale`	No
`collector`	No
`terms_glossary`	No
`any_unavailable`	No
`china_release_alert`	No
`umich_release_alert`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 6, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / china_release_alert

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / crons

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "items": {},
+          "type": "array"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / umich_release_alert

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral detail: it reports pipeline health, staleness, unavailability, and plain-language notices for missed scheduled updates, which goes beyond a generic 'get status' phrasing. No contradictions with annotations.

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?

The description is rich but every sentence earns its place: the first defines the resource and its contents, the second adds pipeline and notice behavior, the third clarifies when to use it. It is front-loaded with the most identifying phrase and contains no filler or tautology.

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 no parameters, a read-only annotation, and an existing output schema, the description fully covers what an agent needs: what is returned, the scope ('every data source'), and the decision context. Nothing essential is missing for correct invocation.

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?

There are zero parameters and the schema is empty, so the description has no parameter burden. The description instead explains what the output covers, which is the relevant semantic content for a no-argument health-check tool. The no-parameters baseline of 4 applies.

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 names a concrete resource ('Freshness status for every data source Jawz reads') and a specific verb/action implied by reporting status. It enumerates concrete artifacts (per-source release date, latest observation date, expected cadence, age in days) that clearly distinguish it from sibling data-retrieval tools. The 'Applies when...' clause further anchors its purpose.

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?

The description gives an explicit applicability condition: use when the reliability of a figure depends on how current its underlying data is. It does not explicitly contrast with sibling tools or name when not to use it, but the stated context is enough to guide selection among the many get_* siblings.

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

All jawz tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?