divux

Place: hazards, weather, schools, parks and the night sky

check_place

Read-only

Returns, for a US city and state or ZIP code (point checks such as the flood zone are for the area's center, not one home): flood zone, FEMA National Risk Index ratings, National Weather Service alerts, air quality, crime rate, drinking water, internet providers, electricity price, home-price trends, EV chargers, county health, childcare prices and nearby HUD housing counselors. A point outside the US returns earthquakes, GDACS disaster alerts within 500 km and the 10-day weather risk. Optional parts, when those inputs are present: a US national park (alerts, closures, fees, campgrounds); night sky at an area's center (aurora chance, moon, darkness, tides); public schools nearby (not school assignment or test scores); a US college (net price after aid, graduation rate, debt, earnings, and a major when supplied). compare_to sets a second US city or ZIP code beside the first and lists the numbers that differ. Applies to questions about conditions and services in a US city or ZIP code, a national park, the night sky, nearby schools or a US college. Results report what the official sources say and are not a safety assessment or an insurance quote.

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

Input Schema

Name	Required	Description
`sky`	No	true for the night sky at the point: aurora chance, moon, darkness and, on US coasts, tides
`park`	No	A US national park or site's name or 4-letter NPS code, e.g. 'Yosemite', 'mora'
`level`	No	School level, with schools
`limit`	No	How many schools
`major`	No	A field of study at the college, for what its graduates earn and borrow, e.g. 'nursing'
`place`	No	Name of the place, for the answer
`state`	No	Two-letter state to narrow a common college name, e.g. 'WA'
`college`	No	A US college's name, e.g. 'University of Washington', 'Rice University'
`schools`	No	true for public schools near the area center, closest first
`location`	No	A US city and state or a ZIP code, e.g. 'Austin, TX' or '78701'.
`compare_to`	No	A second US city and state or ZIP code, to set next to `location` and list the numbers that differ. Not a ranking.
`radius_miles`	No	School search radius, default 2

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / schools / description

Previous value: -"true for public schools near the address or point, closest first"New value: +"true for public schools near the area center, closest first"

Changed6 schema fields changedNov 3, 2026

removedInput schema / properties / address

Removed value: -{
-  "description": "US street address with city and state, e.g. '1600 Pennsylvania Ave NW, Washington, DC 20500'",
-  "maxLength": 200,
-  "type": "string"
-}

changedInput schema / properties / compare_to / description

Previous value: -"A second US street address, to set next to `address` and list the numbers that differ. Not a ranking."New value: +"A second US city and state or ZIP code, to set next to `location` and list the numbers that differ. Not a ranking."

changedInput schema / properties / compare_to / maxLength
```
Previous value: -200New value: +120
```

removedInput schema / properties / lat

Removed value: -{
-  "description": "Latitude, when there's no street address (e.g. the center of a ZIP or city)",
-  "maximum": 90,
-  "minimum": -90,
-  "type": "number"
-}

addedInput schema / properties / location

Added value: +{
+  "description": "A US city and state or a ZIP code, e.g. 'Austin, TX' or '78701'.",
+  "maxLength": 120,
+  "type": "string"
+}

removedInput schema / properties / lon

Removed value: -{
-  "description": "Longitude, with lat",
-  "maximum": 180,
-  "minimum": -180,
-  "type": "number"
-}

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / compare_to

Added value: +{
+  "description": "A second US street address, to set next to `address` and list the numbers that differ. Not a ranking.",
+  "maxLength": 200,
+  "type": "string"
+}

Changed7 schema fields changedOct 26, 2026

addedInput schema / properties / college

Added value: +{
+  "description": "A US college's name, e.g. 'University of Washington', 'Rice University'",
+  "maxLength": 120,
+  "minLength": 3,
+  "type": "string"
+}

addedInput schema / properties / level

Added value: +{
+  "description": "School level, with schools",
+  "enum": [
+    "elementary",
+    "middle",
+    "high"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "How many schools",
+  "maximum": 15,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / major

Added value: +{
+  "description": "A field of study at the college, for what its graduates earn and borrow, e.g. 'nursing'",
+  "maxLength": 60,
+  "type": "string"
+}

addedInput schema / properties / radius_miles

Added value: +{
+  "description": "School search radius, default 2",
+  "maximum": 15,
+  "minimum": 0.5,
+  "type": "number"
+}

addedInput schema / properties / schools

Added value: +{
+  "description": "true for public schools near the address or point, closest first",
+  "type": "boolean"
+}

addedInput schema / properties / state

Added value: +{
+  "description": "Two-letter state to narrow a common college name, e.g. 'WA'",
+  "maxLength": 2,
+  "type": "string"
+}

Changed3 schema fields changedOct 26, 2026

addedInput schema / properties / park

Added value: +{
+  "description": "A US national park or site's name or 4-letter NPS code, e.g. 'Yosemite', 'mora'",
+  "maxLength": 80,
+  "minLength": 3,
+  "type": "string"
+}

addedInput schema / properties / place

Added value: +{
+  "description": "Name of the place, for the answer",
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / sky

Added value: +{
+  "description": "true for the night sky at the point: aurora chance, moon, darkness and, on US coasts, tides",
+  "type": "boolean"
+}

AddedOct 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only/open-world/no-destruction, and the description adds real context beyond them: point checks reflect the area's center rather than a specific home, non-US points return a different result set (earthquakes, GDACS within 500 km, 10-day weather risk), and compare_to lists differences rather than ranking. It does not discuss result sizing or failure modes for ambiguous locations, keeping it below a 5.

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 the core behavior and organized into default outputs, non-US behavior, optional add-ons, and compare mode. The result is dense but a single run-on paragraph with long comma lists, so a reader must parse carefully rather than scan structured segments.

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 12-parameter, multi-mode tool with no output schema, the description covers the US default mode, the non-US branch, each optional mode and its inputs, and compare semantics. It also characterizes returns as source-reported figures rather than assessments. Remaining gaps are minor (no note on which fields are omitted when inputs are absent).

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by tying parameters to outcomes — 'park' yields alerts, closures, fees and campgrounds; 'sky' yields aurora/moon/darkness/tides; 'major' adds graduate earnings and borrowing; 'compare_to' sets a second city beside the first. This is meaningfully more than the schema's short field hints.

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 concrete verb ('Returns') and enumerates the exact resources covered (flood zone, NRI ratings, NWS alerts, air quality, crime, water, internet, electricity, home prices, EV chargers, county health, childcare, HUD counselors). The domain is unmistakably place-condition checking, which cleanly separates it from every sibling (check_car, check_company, check_rates, etc.).

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?

Gives an explicit usage clause: 'Applies to questions about conditions and services in a US city or ZIP code, a national park, the night sky, nearby schools or a US college,' and clarifies the non-US fallback behavior. It also bounds scope with 'not school assignment or test scores' and 'not a safety assessment or an insurance quote.' It does not name sibling tools as alternatives, so it stops short of a 5.

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

All divux 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?