jawz

Get growth indicators

get_growth_indicators

Read-only

Growth pillar indicators, the detail behind the Business cycle card of get_dashboard (its Growth, Jobs and Investment rows) and the regime's Mood row: industrial production (IPMAN, the ISM proxy), consumer sentiment (U Michigan), the 2s10s yield curve, initial claims, plus the Atlanta Fed GDPNow nowcast of the quarter in progress. growth_vote_inputs holds the three inputs of the business cycle's growth vote, each with its word and dated observation: output (IPMAN three-month change), jobs (initial claims four-week average against twelve weeks earlier) and investment (BEA real private fixed investment in information-processing equipment and software, A679RX1Q020SBEA, year on year, with its quarter), plus the vote's rule; the vote itself is applied in get_macro_regime. GDPNow carries its own reference_quarter, the publication date of the estimate, and the previous estimate of the SAME quarter, so its direction of travel is readable; it is reported, not scored, so it does not move the classification. When no estimate is on file the block reports status: unavailable and says so in staleness_flags — not published, which is not the same as zero. Returns classification (green/yellow/red), the growth pillar's own score, separate from the vote; read_complete is false when a series failed to read.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`as_of`	No
`gdpnow`	No
`data_sources`	No
`read_complete`	No
`classification`	No
`terms_glossary`	No
`staleness_flags`	No
`ism_manufacturing`	No
`growth_vote_inputs`	No
`leading_indicators`	No
`consumer_sentiment_umcsent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedOutput schema / properties / growth_vote_inputs

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

addedOutput schema / properties / read_complete

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

Changed1 schema field changedSep 6, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the read-only, closed-world safety profile, and the description adds real value on top: GDPNow 'is reported, not scored, so it does not move the classification', missing estimates report status: unavailable rather than zero, and read_complete goes false when a series fails. These are non-obvious behaviors an agent would otherwise have to guess.

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?

The purpose is front-loaded, but the body is a dense run-on block stitched together with semicolons and parentheticals that is hard to scan. Most content earns its place, yet the structure obscures more than it needs to for a description this long.

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 no-arg, output-schema-backed tool, the description is unusually complete: it names the blocks returned, the classification score separate from the vote, the staleness_flags behavior for missing estimates, and the read_complete failure signal. Nothing needed to interpret or invoke the tool 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?

Zero parameters, so the baseline is 4. The description goes further by naming the underlying series codes and derived quantities (four-week average vs twelve weeks earlier, year-on-year A679RX1Q020SBEA), giving context for the returned fields even though no invocation arguments exist.

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?

States a specific verb+resource ('Growth pillar indicators') and immediately locates it in the tool hierarchy as the detail behind get_dashboard's Business cycle card and the regime's Mood row. The constituent series and the growth_vote_inputs block are named, so an agent can distinguish it from get_macro_regime and get_dashboard without opening a schema.

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

Usage Guidelines3/5

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

Usage is implied through the relationship statements ('applied in get_macro_regime', 'the detail behind the Business cycle card of get_dashboard'), which positions the tool but never says explicitly when to reach for it versus those siblings. No when-not or prerequisite guidance is given.

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?