Skip to main content
This is a workflow contract, not a live result. It does not guarantee nationwide charging coverage, real-time data, currently available chargers or distance-ranked results.

​
Users and inputs

Product teams and automation partners repeatedly checking Korean regional environmental information are the intended users. Inputs include a Korean region name or coordinates, weather issue date/time, forecast target time and a verified air-monitoring station name. resolve_location can normalize location into weather-grid/administrative codes, but does not automatically establish an air-monitoring station. Invalid coordinates and ambiguous names require clarification. This contract requests all four components: location, weather, air quality and charging stations. Acceptable adoption means an operator confirms using a briefing that explicitly preserves differing times, geographic scope and omissions. Recommendations, safety guarantees, reservations, medical judgments and route optimization are out of scope. Raw addresses, coordinates, queries and keys are excluded from optional analytics.

​
Existing guides and tools

  1. Reuse AI connection and first tool authentication/activation.
  2. Check resolve_location coverage and ask the user to disambiguate locations.
  3. Use weather/village-forecast, getVillageForecast in the weather catalog and the existing weather widget. Distinguish forecasts from observations.
  4. Read station and measurement time with environment/air-quality-realtime, getAirQualityRealtimeByStation in the environment catalog.
  5. transportation/ev-charging, getEvCharging in the transportation catalog covers Suwon. Other regions are unsupported_region.
  6. Preserve reference times and missing-data reasons for human review. Fetching results and adopting them are separate actions.
Station coordinates/addresses do not make the provider query a distance-ranked or charger-availability search. Determining nearby stations needs separately verified coordinates/distance computation; that was not executed for this example.

​
Sources, time, permissions and cost

Repository metadata review date: 2026-10-10. No live provider smoke was performed. An owner must check keys, provider application/quota, terms and redistribution rights. Check personal/managed-key availability and Bridger pricing/support before execution. This page contains no rights approval or free/unlimited guarantee. Agree and document freshness limits per component and use case; HTTP response time is not measurement time.

​
Outcome contract

This page and synthetic fixtures describe a proposed normalized envelope, not changes to current MCP responses or connectors. Each requested component includes source, asOf and unavailable. Unsupported regions and stale data are not successful rows. Unknown reference times remain missing_asof; never insert the current time to disguise them. Partial results are not complete/first successes. Review again after input/key correction or approved retries.

​
Offline evidence and support

The evidence pack includes 25 synthetic cases for this bundle. Rows and reference times are invented for tests, not measurements, coordinates, addresses or provider responses; they do not verify provider wire schemas or live state. Cases include unsupported regions, missing keys, ambiguous locations, empty responses, stale values, unknown reference times and provider errors. Do not claim production readiness before rights, keys, the missing attachment, real smoke and support ownership are checked. Related: Business basics check, authentication and security, BYOAPI.