Smarter Weather

Find places

find_places

Read-onlyIdempotent

Find places: a name, ZIP, venue or address to ranked candidates with lat/lon, or coordinates to the place and timezone. Pass query or lat+lon; rows carry type place|zip|address|poi|county|station, matched_via: "autosuggest" marks fallback rows and partial a timed-out section. Weather tools take location; use this to disambiguate or name a point. Example: {"lat": 39.74, "lon": -104.99} -> Denver, Colorado, America/Denver.

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

Input Schema

Name	Required	Description
`lat`	No	Latitude (-90 to 90), with lon; not with query.
`lon`	No	Longitude (-180 to 180), with lat.
`fuzzy`	No	Query only: autosuggest for partial or misspelled input. Default false.
`limit`	No	Query only: how many candidates (1-10). Default 5.
`query`	No	Place name, ZIP or venue/address (1-200 characters); not with lat/lon.
`include`	No	boundaries: each row's state, county and zone ids for get_data's area.
`near_lat`	No	Query only: rank near this point (-90 to 90); with near_lon.
`near_lon`	No	Longitude of near_lat (-180 to 180).

Output Schema

Name	Required	Description
`lat`	No
`lon`	No
`query`	No
`partial`	No	Sections that did not finish, e.g. {"poi": "timeout"}; the list may be incomplete.
`candidates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed2 schema fields changedOct 30, 2026

addedInput schema / properties / include

Added value: +{
+  "description": "boundaries: each row's state, county and zone ids for get_data's area.",
+  "items": {
+    "enum": [
+      "boundaries"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / candidates / items / properties / boundaries

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "description": "With include boundaries: containing-boundary ids per reference layer (state, county, zone, office), each an `area` reference get_data takes as {product, feature_id}.",
+  "properties": {},
+  "type": "object"
+}

AddedOct 29, 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 safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new behavior: rows carry `matched_via: "autosuggest"` for fallback results and `partial` for a timed-out section. That degraded-result disclosure is valuable; it stops short of explaining pagination or what happens when no arguments are supplied.

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 the two modes, then output row semantics, then cross-tool relevance, then an example — a sensible order with no filler sentences. The telegraphic phrasing ('rows carry `type` ... `partial` a timed-out section') is dense but readable, and the example earns its space for the coordinate mode.

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 an 8-parameter, zero-required lookup with an output schema and full annotations, the description covers mode selection, result-row meaning, and how siblings consume the output. The one gap is that with no required parameters it never states what an empty call returns or errors with.

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 coverage is 100%, so every parameter is already documented, including the mutual exclusivity of `query` vs `lat`/`lon`. The description reinforces the either/or rule and adds a concrete coordinate example, but contributes little semantic meaning beyond the schema's own text.

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?

Names a specific verb and resource and spells out both operating modes: text (name/ZIP/venue/address) to ranked candidates with lat/lon, and coordinates to a place plus timezone. It also distinguishes itself from the weather siblings by noting they take `location`, so an agent can route without opening schemas.

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?

States the two calling forms ('Pass `query` or `lat`+`lon`') and gives the downstream use case: 'Weather tools take `location`; use this to disambiguate or name a point.' That is clear context plus an alternative, but it does not say when fuzzy/limit/near_* ranking should be preferred, so no explicit exclusion guidance.

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

All Smarter Weather 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.