Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_stop_climate

Idempotent

Stop remote climate control (Kia rems/stop, 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…

Instructions

Stop remote climate control (Kia rems/stop, 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 false (there is no flat airCtrlOn field); ign3 — the EV ignition proxy — is reported alongside. commandAccepted (Kia took the request) and stateConfirmed (the car actually reads stopped) are separate. State changes were observed to take 30–60s.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vehicle_keyYesThe 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.
waitSecondsNoHow 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.
confirmTokenNoONLY 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.5
    • 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"
+]
  2. Changed2 schema fields changedv1.1.0
    • 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"
+}
  3. Changed2 schema fields changedv1.0.3
    • 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."
  4. Changed1 schema field changedv0.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (non-destructive, idempotent, open-world), but the description goes well beyond: the confirm-gating behavior, the distinction between commandAccepted and stateConfirmed, the nested climate.airCtrl field vs. the non-existent airCtrlOn, the ign3 EV ignition proxy, and the observed 30–60s state-change latency.

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?

It's a dense paragraph but every sentence carries operational weight: confirmation flow, field names, accepted-vs-confirmed distinction, and timing. It is front-loaded with the core action and endpoint. Slightly long, but no filler sentences.

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?

Although there is no output schema, the description supplies the critical post-command behavior (re-reading cmm/gvi, nested airCtrl field, commandAccepted vs stateConfirmed) and latency that an agent needs to interpret results correctly. Nothing essential for correct invocation is missing.

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 100%, so the baseline is 3, but the description adds real meaning: confirmToken is only for the fallback flow and must never be reused or invented, and waitSeconds relates to the 30–60s observed propagation. The parameter semantics are reinforced rather than merely repeated.

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?

The description states a specific verb and resource — 'Stop remote climate control' — names the exact Kia endpoint (rems/stop), and implicitly distinguishes itself from the sibling kia_start_climate. An agent can identify the tool's job 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains when the confirmation flow applies: elicitation clients get a prompt, others get a no-network preview plus confirmToken, and a repeat call is required. It doesn't explicitly contrast with kia_start_climate or failure-recovery alternatives, but the confirm-mode branching is thorough contextual guidance.

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

Deploy Server

Other Tools