Pressure Atlas

Get recent pressure

get_recent_pressure

Read-only

Daily pressure for a window, as compact CSV (one row per day: the state, expanded, released, equilibrium, pressurized, or compressed, then its flow, building or releasing, and whether that movement was accelerating or slowing). Serves the days your access includes; list_datasets states the depth. Readings are measurements of conditions, not predictions or recommendations.

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": "get_recent_pressure"
  }
}

Input Schema

Name	Required	Description	Default
`dataset`	No	Dataset slug from list_datasets. Defaults to "macro".	macro
`date_end`	No	Last day of the window (YYYY-MM-DD, inclusive, UTC). Defaults to the newest closed day your access includes; a later day is cut to it.
`date_start`	No	First day of the window (YYYY-MM-DD, inclusive, UTC).

Output Schema

Name	Required	Description	Default
`rows`	Yes	One row per closed UTC day, ascending.
`dataset`	Yes	Dataset slug.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

changedOutput schema / properties / rows / items / properties / label / description

Previous value: -"expanded, released, equilibrium, pressurized, or compressed."New value: +"The state, lowest first: expanded, released, equilibrium, pressurized, or compressed."

changedOutput schema / properties / rows / items / properties / pressure / description

Previous value: -"The state, a whole number 1-5."New value: +"Not sent; the state is label."

changedOutput schema / properties / rows / items / required

Previous value: -[
-  "date",
-  "pressure",
-  "label"
-]New value: +[
+  "date",
+  "label"
+]

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / date_end / description

Previous value: -"Last day of the window (YYYY-MM-DD, inclusive, UTC). Defaults to the latest closed day; the fixed recent window ignores explicit dates."New value: +"Last day of the window (YYYY-MM-DD, inclusive, UTC). Defaults to the newest closed day your access includes; a later day is cut to it."

Changed3 schema fields changedOct 1, 2026

changedOutput schema / properties / rows / items / properties / label / description

Previous value: -"expanding, releasing, equilibrium, building, or compressing."New value: +"expanded, released, equilibrium, pressurized, or compressed."

changedOutput schema / properties / rows / items / properties / pace / description

Previous value: -"rising or slowing; absent when the day has no pace."New value: +"accelerating or slowing; absent when the day has no pace."

changedOutput schema / properties / rows / items / properties / pressure / description
```
Previous value: -"0-5, one decimal."New value: +"The state, a whole number 1-5."
```

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly true, destructive false, openWorld false), so the bar is lower; the description still adds real behavioral context — the value space for each row (state, flow, acceleration), the CSV-per-day granularity, and the access-scoped depth constraint. The closing caveat that readings are measurements, not predictions or recommendations, further clarifies semantics.

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

Conciseness4/5

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

Front-loaded with purpose and output format, then access constraints, then the semantic caveat. The parenthetical enumeration of state values is dense but informative; the whole thing is three sentences with minimal waste.

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

Completeness4/5

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

With an output schema present, return values needn't be explained, yet the description usefully characterizes the CSV layout and field domains. Combined with the access-depth pointer to list_datasets and the annotations covering safety, the definition is nearly complete; only the sibling routing is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents dataset, date_start, and date_end with patterns, defaults, and inclusivity. The description only restates the window concept and access depth, adding no new syntax or format detail beyond the schema. Baseline 3 applies.

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 a specific verb and resource ('Daily pressure for a window') plus the output shape ('compact CSV, one row per day'), so an agent knows exactly what it returns. It does not, however, name or distinguish itself from the obvious sibling get_latest_pressure, which differs only by scope.

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?

There is implied usage — it serves the window of days your access includes — and it points to list_datasets for determining depth, which is a useful prerequisite hint. But it never states when to prefer this over get_latest_pressure or fetch, and gives no explicit exclusions.

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

All Pressure Atlas tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?