Kia Access MCP

kia_start_climate

Idempotent

Instructions

Start remote climate control / preconditioning (Kia rems/start, live-verified). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call makes NO network call and returns a preview plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Once confirmed it sends the command and re-reads cmm/gvi until the NESTED climate.airCtrl reads true (there is no flat airCtrlOn field). On an EV engine stays false while climate runs — ign3 is the ignition proxy and is reported alongside. commandAccepted (Kia took the request) and stateConfirmed (the car actually reads running) are separate; state changes were observed to take 30–60s. TEMPERATURE IS BEST-EFFORT AND UNCONFIRMED: per docs/KIA-API.md a start requesting 70°F still read back 72°F, so the car may report its own last-set target rather than the requested one — do not promise the user a specific cabin temperature. Seat and steering-wheel/rear-window heating are not sent at all: the request body deliberately omits heatVentSeat (Kia validates seat capability per car) and leaves every heatingAccessory field at 0.

Input Schema

TableJSON Schema

Name	Required	Description
`defrost`	No	Run front defrost (default false).
`temperature`	No	Target cabin temperature in °F, 62–82, or the sentinel "LOW"/"HIGH" for the ends of the range (default 70). A quoted whole number ("72") is accepted and treated as the number. BEST-EFFORT / UNCONFIRMED — see docs/KIA-API.md.
`vehicle_key`	Yes	The vehicle key (`vehicleKey` from the vehicle-list tool), used as the `vinkey` header. Not the VIN. Required: commands never default to the only vehicle, so every request names the car it acts on.
`waitSeconds`	No	How long to keep re-reading cmm/gvi for proof the command landed (default 30). Observed changes took 30–60s, so an unconfirmed result is common — re-read the vehicle status rather than re-sending the command. Values above ~45 can outlast an MCP client's own request timeout (often 60s), which then reports a failure for a command that WAS sent. 0 checks once and returns immediately — the command may still land afterwards.
`confirmToken`	No	ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
`durationMinutes`	No	Minutes the ignition stays on (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.1.5Oct 13, 2026

addedInput schema / properties / vehicle_key

Added value: +{
+  "allOf": [
+    {
+      "pattern": "^[^/?#\\s]+$"
+    },
+    {
+      "pattern": "^[!-~]+$"
+    }
+  ],
+  "description": "The vehicle key (`vehicleKey` from the vehicle-list tool), used as the `vinkey` header. Not the VIN. Required: commands never default to the only vehicle, so every request names the car it acts on.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / vinKey

Removed value: -{
-  "description": "The vehicle key (`vehicleKey` from the vehicle-list tool), used as the `vinkey` header. Not the VIN.",
-  "minLength": 1,
-  "pattern": "^[^/?#\\s]+$",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "vinKey"
-]New value: +[
+  "vehicle_key"
+]

Changed2 schema fields changedv1.1.0Sep 24, 2026

removedInput schema / properties / confirm

Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}

addedInput schema / properties / confirmToken

Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}

Changed2 schema fields changedv1.0.3Sep 24, 2026

changedInput schema / properties / waitSeconds / default
```
Previous value: -60New value: +30
```

changedInput schema / properties / waitSeconds / description

Previous value: -"How long to keep re-reading cmm/gvi for proof the command landed (default 60). Observed changes took 30–60s. 0 checks once and returns immediately — the command may still land afterwards."New value: +"How long to keep re-reading cmm/gvi for proof the command landed (default 30). Observed changes took 30–60s, so an unconfirmed result is common — re-read the vehicle status rather than re-sending the command. Values above ~45 can outlast an MCP client's own request timeout (often 60s), which then reports a failure for a command that WAS sent. 0 checks once and returns immediately — the command may still land afterwards."

Changed1 schema field changedv0.9.0Sep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv0.6.1Aug 11, 2026

changedInput schema / properties / temperature / anyOf

Previous value: -[
-  {
-    "maximum": 82,
-    "minimum": 62,
-    "type": "integer"
-  },
-  {
-    "enum": [
-      "LOW",
-      "HIGH"
-    ],
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 82,
+    "minimum": 62,
+    "type": "integer"
+  },
+  {
+    "enum": [
+      "LOW",
+      "HIGH"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]

changedInput schema / properties / temperature / description

Previous value: -"Target cabin temperature in °F, 62–82, or the sentinel \"LOW\"/\"HIGH\" for the ends of the range (default 70). BEST-EFFORT / UNCONFIRMED — see docs/KIA-API.md."New value: +"Target cabin temperature in °F, 62–82, or the sentinel \"LOW\"/\"HIGH\" for the ends of the range (default 70). A quoted whole number (\"72\") is accepted and treated as the number. BEST-EFFORT / UNCONFIRMED — see docs/KIA-API.md."

First observedv0.1.0Jul 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes far beyond the annotations: discloses the 30–60s state-change lag, that commandAccepted and stateConfirmed are distinct, that waitSeconds can outlast a client timeout and report false failure, that the confirmable two-step preview makes no network call, and that seat/steering/rear-window heating are deliberately omitted. Annotations only cover safety hints, so this context is highly valuable.

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-loads the purpose and confirmation flow, but the final sentence about omitted heating fields is long and the doc-reference caveats accrete. Most sentences earn their place, though it leans dense with parenthetical asides.

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?

Covers everything needed to invoke correctly: confirmation mechanics, polling behavior, timeout pitfalls, misleading field names (no flat airCtrlOn, ign3 as ignition proxy on EVs), and the best-effort temperature caveat. No output schema exists, and the description adequately describes what to expect back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning the schema lacks: temperature is best-effort/unconfirmed (70°F read back as 72°F), waitSeconds can outlive a client timeout and the correct recovery is re-reading status rather than re-sending, and confirmToken must only be passed after explicit user approval. It doesn't re-explain vehicle_key, which the schema already covers.

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 the specific verb+resource (start remote climate control / preconditioning) and pins it to the Kia rems/start endpoint. It is unambiguous against siblings like kia_stop_climate, and it names the nested field (climate.airCtrl) that defines success.

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?

Explains the confirmation flow and how to proceed when a client lacks elicitation (preview + confirmToken then repeat). It doesn't explicitly compare against kia_stop_climate or state when the user would want climate preconditioning versus charging, but the operational when-to-use guidance is clear.

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

Deploy Server

kia_start_climate

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools