Smarter Weather

Search locations

search_locations

Read-onlyIdempotent

Resolve a place to ranked candidates with lat/lon: city ("Denver"), "city, ST", ZIP ("50219"), or partial input with fuzzy=true ("bost" -> Boston); venues and addresses where enabled. Rows carry type place|zip|address|poi; pass a row's lat/lon to weather tools. matched_via: "autosuggest" marks rows found after the exact match missed; partial means a section timed out. Weather tools take location directly, venues included -- use this to disambiguate ("which Springfield?") or present choices.

Input Schema

Name	Required	Description
`fuzzy`	No	Autosuggest mode for partial/misspelled input. Default false (exact search).
`limit`	No	Maximum candidates to return (1-10). Default 5.
`query`	Yes	Place query: city, "city, state", ZIP, partial text, or venue/address where enabled.
`near_lat`	No	Rank venues/addresses near this point; pair with near_lon.
`near_lon`	No

Output Schema

Name	Required	Description
`query`	Yes
`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.

Changed2 schema fields changedOct 22, 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#"

Changed3 schema fields changedOct 22, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / properties / candidates / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / partial / properties
```
Added value: +{}
```

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / near_lat

Added value: +{
+  "description": "Rank venues/addresses near this point; pair with near_lon.",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

addedInput schema / properties / near_lon

Added value: +{
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

changedInput schema / properties / query / description

Previous value: -"Place query: city, \"city, state\", ZIP, venue, address, or partial text."New value: +"Place query: city, \"city, state\", ZIP, partial text, or venue/address where enabled."

Changed8 schema fields changedOct 13, 2026

changedInput schema / properties / query / description

Previous value: -"Place query: city, \"city, state\", ZIP, or partial text with fuzzy=true."New value: +"Place query: city, \"city, state\", ZIP, venue, address, or partial text."

addedOutput schema / properties / candidates / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / candidates / items / properties / matched_via

Added value: +{
+  "const": "autosuggest",
+  "description": "Set on exact-search rows found by the venue/address fallback.",
+  "type": "string"
+}

changedOutput schema / properties / candidates / items / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / candidates / items / properties / state / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / candidates / items / properties / subtitle
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / candidates / items / properties / title
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / partial

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Sections that did not finish, e.g. {\"poi\": \"timeout\"}; the list may be incomplete.",
+  "type": "object"
+}

Changed1 schema field changedSep 1, 2026
- changedOutput schema / properties / candidates / items / additionalProperties
```
Previous value: -falseNew value: +true
```
Changed1 schema field changedAug 17, 2026
- addedOutput schema / properties / candidates / items / properties / place_id
```
Added value: +{
+  "type": "string"
+}
```
First observedJul 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior; the description adds meaningful fallback semantics: `matched_via: "autosuggest"` marks rows found after an exact miss, and `partial` means a section timed out. It also explains fuzzy/autosuggest mode without contradicting 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.

Conciseness4/5

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

The core purpose is front-loaded, and the sentences carry useful query formats, output flags, and weather-tool guidance without obvious filler. It is dense and semicolon-heavy, but still efficient for the amount of context it conveys.

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?

Given the rich annotations and an output schema, the description supplies enough context for correct invocation: purpose, accepted inputs, fallback flags, and how to use results with weather tools. The only remaining gap is minor `near_lon` detail, which is partly covered by the schema's `near_lat` pairing.

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 80% and the schema already documents `fuzzy`, `limit`, `query`, and `near_lat`, while `near_lon` lacks a description. The description reinforces query formats and fuzzy usage but does not add much beyond the schema or clarify the missing `near_lon` semantics, so the high-coverage baseline of 3 is appropriate.

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 and resource: 'Resolve a place to ranked candidates with lat/lon,' lists accepted query forms, and names the row types returned. It clearly establishes forward place search and its relation to weather tools, so an agent can distinguish it from reverse_geocode without opening the schema.

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?

Explicitly says weather tools take `location` directly and that this tool should be used to disambiguate or present choices, which gives a clear when-to-use vs. alternative condition. It also explains `fuzzy=true` for partial input, making the usage context concrete.

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.