sunshade

Open / close / position / sync the sunshade

Open, close, set the sunshade to a position, or synchronise it to the sunroof. Requests range from a fully specified open to an unstated percentage, a "match the sunroof" sync, or a case where the control — or its position parameter — is missing. The same method handles all of these.

When this applies

• "Open the sunshade to N%" / "close the sunshade" — a fully specified move.
• "Open the sunshade for some shade" — no percentage given.
• "Match / synchronise the sunshade to the sunroof" — set the sunshade to the sunroof's current position.
• Asking for the sunshade's position.

Tools

• get_user_preferences() — read the default opening percentage only when the percentage is meant to come from a standing preference.
• get_sunroof_and_sunshade_position() — read the current sunroof and sunshade positions; required before any "match/synchronise to the sunroof" request — the target number is only knowable from this read. A field may read "unknown" — unverifiable, not a value.
• get_weather(...) — read weather for the relevant place/time only when a condition or warning applies to the move.
• open_close_sunshade({percentage}) — set the sunshade opening percentage; 0 is fully closed. The tool, or its position parameter, may be missing (a missing required parameter makes every call error).

Method

1. Act on the sunshade, with the correct argument. Open vs. close, and the right percentage value — don't close when an open was asked, and don't omit the value.
2. "Match/synchronise the sunshade to the sunroof" → read positions FIRST, then set the sunshade. Call get_sunroof_and_sunshade_position once, take the sunroof's current position as the target, and set the sunshade to it — the sunshade is the component that moves. Don't skip the read and don't ask or guess the target; the number comes from the reading. This holds even if the user also states a number ("set the sunshade to 60% to match the sunroof") — the "match" framing makes the sunroof the source of truth, so still read and use the read value; the stated number is the user's belief, not the authority. Only a plain positioning request with no "match" framing skips the read.
3. Read state/weather only when the outcome depends on it, once. Read positions for a sync; read weather one time only if a condition or warning applies. Read each deciding value once.