DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber

Water Risk

get_water_risk

Read-onlyIdempotent

FRONT DOOR CHECK — if you need a SITE VERDICT spanning grid + fiber + water + tax + climate, call execute_plan(intent="<the user's question, unchanged>") rather than hand-chaining this with its siblings. If you want the WATER factor on its own, get_water_risk IS the right call — one round trip, free tier, no planner overhead. Use when scoring a US site for cooling-water sustainability — the water-risk factor engineering site-selectors screen before committing to evaporative cooling. Example: "Is this Phoenix parcel water-constrained for a 100MW build?" — get_water_risk lat=33.45 lon=-112.07 (or get_water_risk state=AZ / county=Maricopa). Params: ONE of lat+lon (-90..90 / -180..180), state (2-letter US), or county; lat/lon gives the most precise read. Returns: {water_stress_score (0-100, higher=worse), drought_category (D0-D4), outlook_12mo, cooling_water_assessment, source}. Joined to USGS water-stress + US Drought Monitor. Free tier. Do NOT use for nearby physical infrastructure (use get_infrastructure) or a combined multi-factor site verdict spanning grid+fiber+water+tax+climate (use analyze_site); this covers the WATER factor only.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Site latitude in decimal degrees (-90 to 90) for the most precise water-risk read, e.g. 33.45
`lng`	No	Alias for lon — either name works
`lon`	No	Site longitude in decimal degrees (-180 to 180), e.g. -112.07
`state`	No	US state abbreviation as an alternative to lat/lon, e.g. AZ
`mpp_pay`	No	Autonomous payment (Stripe MPP), step 1: set true to receive a signed $0.50 payment challenge for this call instead of the free preview. No money moves — a challenge is a price quote. Humans never set this, so it does not affect the normal free/trial funnel.
`latitude`	No	Alias for lat — either name works
`longitude`	No	Alias for lon — either name works
`mpp_credential`	No	Autonomous payment (Stripe MPP), step 2: the Shared Payment Token you minted for challenges[0]. Set it here to pay $0.50 for this single call and receive the full result — no API key, no subscription, no human. One payment covers one call.

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier) when available.
`_entity`	No	Payload class discriminator (e.g. facility\|market\|iso_grid\|queue_results\|deal\|report\|response) — branch on this before parsing the rest.
`citation`	No	Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself.
`provenance`	No	Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
`_front_door`	No	In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
`_return_loop`	No	Suggested next-session delta call (get_changes since=24h) so you pull only what changed.
`site_evaluation_handoff`	No	Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 8, 2026

addedInput schema / properties / mpp_credential

Added value: +{
+  "description": "Autonomous payment (Stripe MPP), step 2: the Shared Payment Token you minted for challenges[0]. Set it here to pay $0.50 for this single call and receive the full result — no API key, no subscription, no human. One payment covers one call.",
+  "type": "string"
+}

addedInput schema / properties / mpp_pay

Added value: +{
+  "description": "Autonomous payment (Stripe MPP), step 1: set true to receive a signed $0.50 payment challenge for this call instead of the free preview. No money moves — a challenge is a price quote. Humans never set this, so it does not affect the normal free/trial funnel.",
+  "type": "boolean"
+}

Changed2 schema fields changedAug 21, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed5 schema fields changedAug 11, 2026

removedOutput schema / properties / citation / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / citation / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]

changedOutput schema / properties / citation / description

Previous value: -"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload."New value: +"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself."

removedOutput schema / properties / citation / properties
```
Removed value: -{}
```
removedOutput schema / properties / citation / type
```
Removed value: -"object"
```

Changed1 schema field changedJul 21, 2026

addedOutput schema / properties / _front_door

Added value: +{
+  "additionalProperties": {},
+  "description": "In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.",
+  "properties": {},
+  "type": "object"
+}

Changed5 schema fields changedJul 18, 2026

removedOutput schema / properties / site_evaluation_handoff / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / site_evaluation_handoff / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  }
+]

changedOutput schema / properties / site_evaluation_handoff / description

Previous value: -"Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates."New value: +"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."

removedOutput schema / properties / site_evaluation_handoff / properties
```
Removed value: -{}
```
removedOutput schema / properties / site_evaluation_handoff / type
```
Removed value: -"object"
```

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "DC Hub envelope: structuredContent mirrors the JSON payload in content[0].text — tool-specific data fields ride at the top level alongside these envelope keys.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.",
+      "type": "string"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Suggested next-session delta call (get_changes since=24h) so you pull only what changed.",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "additionalProperties": {},
+      "description": "Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload.",
+      "properties": {},
+      "type": "object"
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier) when available.",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "additionalProperties": {},
+      "description": "Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedJul 16, 2026

addedInput schema / properties / latitude

Added value: +{
+  "description": "Alias for lat — either name works",
+  "type": "number"
+}

addedInput schema / properties / lng

Added value: +{
+  "description": "Alias for lon — either name works",
+  "type": "number"
+}

addedInput schema / properties / longitude

Added value: +{
+  "description": "Alias for lon — either name works",
+  "type": "number"
+}

Changed3 schema fields changedJul 2, 2026

addedInput schema / properties / lat / description

Added value: +"Site latitude in decimal degrees (-90 to 90) for the most precise water-risk read, e.g. 33.45"

addedInput schema / properties / lon / description

Added value: +"Site longitude in decimal degrees (-180 to 180), e.g. -112.07"

addedInput schema / properties / state / description

Added value: +"US state abbreviation as an alternative to lat/lon, e.g. AZ"

Changed9 schema fields changedApr 29, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / lat / default
```
Removed value: -0
```
removedInput schema / properties / lat / title
```
Removed value: -"Lat"
```
removedInput schema / properties / lon / default
```
Removed value: -0
```
removedInput schema / properties / lon / title
```
Removed value: -"Lon"
```
removedInput schema / properties / state / default
```
Removed value: -""
```
removedInput schema / properties / state / title
```
Removed value: -"State"
```

removedInput schema / title

Removed value: -"get_water_riskArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_water_riskOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedApr 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_water_riskOutput",
+  "type": "object"
+}

Changed1 schema field changedApr 11, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_water_riskOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedMar 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_water_riskOutput",
+  "type": "object"
+}

Changed1 schema field changedMar 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_water_riskOutput",
-  "type": "object"
-}New value: +null

AddedMar 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: one round trip, free tier, no planner overhead, and data sourced from USGS water-stress and the US Drought Monitor. It does not deeply explain the paid MPP path, but the schema covers that and there is no contradiction with the annotations.

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 description is front-loaded with the most important routing decision and uses examples effectively. However, it is long and somewhat repetitive, repeating the 'grid + fiber + water + tax + climate' phrase and the same exclusion logic in multiple forms. It could be tightened without losing clarity.

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?

For a tool with an output schema and full parameter schema coverage, the description covers the core use case, input modes, precision trade-offs, data sources, and alternatives. The main weakness is the invented 'county' parameter, which creates a false expectation and is not harmless. Overall, the agent has enough context to call the tool correctly for the lat/lon and state paths.

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

Parameters2/5

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

Although the schema has 100% parameter coverage, the description adds meaningful selection semantics like 'ONE of lat+lon, state, or county' and notes that lat/lon gives the most precise read. However, it explicitly recommends a 'county' parameter that does not exist in the input schema, which is misleading and could cause invocation errors. This invalid guidance offsets the useful grouping and precision advice.

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 clearly states that this tool returns the WATER factor for a US site, specifically the water-risk score for cooling-water sustainability. It distinguishes itself from analyze_site, execute_plan, and get_infrastructure by explicitly saying it covers only the water factor. The example with Phoenix makes the purpose concrete and unambiguous.

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 gives explicit when-to-use guidance: use get_water_risk when you need only the water-risk factor for a US site, and use execute_plan or analyze_site for a combined multi-factor verdict. It also names get_infrastructure as the alternative for nearby physical infrastructure. The examples and 'Do NOT use' clauses make selection straightforward.

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

All DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber 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.

Water Risk

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources