Smarter Weather
Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.
| Endpoint | https://mcp.smarterweather.com (streamable-http) |
|---|---|
| Registry version | 0.1.1 |
| Now | 13 tools · grade B (82) · pin ts_127539bfacd49c2a9e96e4b286752009 · protocol 2025-06-18 |
| First / last listed | 2026-11-01 03:28 UTC / 2026-11-01 03:28 UTC |
| Grade over time | 2026-11-01: B (82), 13 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: find_places get_forecast get_current_conditions get_alerts get_observed_precipitation get_forecast_distribution search_data find_tools call_tool describe_data get_data get_status get_time_context
find_places | Find places: a name, ZIP, venue or address to ranked candidates with lat/lon, or coordinates to the place and timezone. Pass `query` (fuzzy=true for partial input) or `lat`+`lon`; rows carry `type` place|zip|address|poi, `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 params: query, lat, lon, fuzzy, limit, near_lat, near_lon, include |
get_forecast | Forecast for a US place: current conditions, daily forecast with sunrise and sunset, active alerts and outlooks in one call, and hour by hour with include=hourly. Blended across NBM, HRRR, GFS, RTMA and SPC and unit-converted server-side; times are UTC ISO 8601, quote daily[].astro.local as local, and if forecast.location.timezone_resolved is false state times as UTC. For hours set `hours` (next N params: location, lat, lon, days, units, include, hours, start, end, view |
get_current_conditions | Current weather right now at a location from two independent sources in one call: the RTMA gridded analysis (exact-point values, updated sub-hourly) and the nearest METAR station observation (ground truth with raw METAR, flight category). Use the analysis for point-accurate values and the station for verification. Analysis fields: temperature_2m, dew_point_2m, relative_humidity_2m (derived here fr params: location, lat, lon, units |
get_alerts | NWS watches, warnings, advisories. Point (city/ZIP/lat+lon): containing polygons. BBox or US state/DC/CONUS (codes, full names, US/national): intersecting polygons. A city miss is not a statewide all-clear — query the state or a bbox; never say regional inventory is impossible. NY/WA and "New York State"/"Washington State" are states; "New York"/"Washington" stay cities. Omit at for now; at (ISO-8 params: location, lat, lon, bbox, events, alert_id, at |
get_observed_precipitation | How much rain fell: observed precipitation totals at a location. Use for "did it rain", "how much rain fell", "rain in the last 24 hours / since yesterday". Source: MRMS MultiSensor QPE Pass2 (radar bias-corrected to rain gauges) over 1/3/6/24/48/72 h windows (CONUS; 1 h only in Alaska and Hawaii). Values have about 2 mm (0.08 in) resolution, so 0 means under about 1 mm; data runs about an hour be params: location, lat, lon, windows, units, at, include_nowcast |
get_forecast_distribution | NBM probabilistic guidance for one weather aspect: percentiles (p10-p90), exceedance probabilities and ensemble spread. Use this for any question about odds, ranges, potential or confidence ("how much could we get", "range of possible highs", "how sure is this") -- a deterministic forecast value cannot answer one. Reading the percentiles: p50 is the most likely outcome, p90 is the reasonable worst params: location, lat, lon, aspect*, hours, units |
search_data | Search the data catalog: which dataset's values answer a weather question, or what data exists at a point. With `query` it ranks grids, radar, satellite, outlooks and observations and returns hits with variable, units, cadence, why, the exact `call` to run next and any verified `example`; without it, it lists datasets at the place with freshness, or every public one. A place (`location` or lat/lon params: query, location, lat, lon, domain, kind, family, limit |
find_tools | Lists the weather tools this connection does not show (best times, routes, air quality; station observations, soundings, hurricane recon; lightning, storm cells, storm reports; outlooks, forecaster text, hurricanes; climate records and normals; forecast accuracy; maps and charts; crop heat units), with when to use each and its required arguments. Run one with call_tool, in this session, no reconne params: tools |
call_tool | Runs a tool find_tools lists, by name: same price, limits and result as calling it directly. Tools already in your list are called directly, not through this. `arguments` follows that tool's input schema. params: tool*, arguments |
describe_data | A dataset's variables or properties (standard names, units, categories, bands, aggregates), horizon, step, cadence, freshness, cost class, verified `examples` and an example_query to read its values. Free; call it after search_data, before get_data. Example: {"dataset_id": "<from search_data>"}. params: dataset_id* |
get_data | Values, totals, comparisons, people and POI counts from any catalog dataset (models, radar, alerts, outlooks, reference layers) at a place or several, over a bbox or area, or as items. `select` takes `product:variable` or `product:property` tokens, a standard name or a concept such as `population`; send one space word (an `area` reference is `{product, feature_id}`) and at most one time word (hour params: select*, location, locations, bbox, area, path, hours, start, end, at, run, step, stats, filter, where, windows, units, view, limit, cursor |
get_status | Data freshness of the weather platform (no inputs needed; refreshed about every 5 minutes): overall state, per-source states (ok / degraded / outage / no_signal), open incidents with their cause (provider outage vs internal processing delay) and active provider advisories. Use it when asked whether data is current, when other tools return stale-looking data, or before presenting time-critical weat params: include_ok |
get_time_context | Complete temporal context for a location: local time, timezone, 14-day calendar with day names and Today/Tomorrow offsets, sunrise/sunset/solar times (from the weather pipeline's astro product), and moon phase. Use whenever you need to reason about dates, times, or daylight for a location -- including "what time is sunset?", "is it dark there now?", or "what day of the week is the 4th-day forecast params: location, lat, lon |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.