Kia Access MCP

kia_stop_charge

Idempotent

Instructions

Ask the vehicle to stop charging (evc/cancel). Verified against a charging vehicle: evStatus.batteryCharge goes false within ~30-60s. Confirm with kia_vehicle_status rather than trusting the success status. 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).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vehicle_key": "<vehicle_key>"
    },
    "name": "kia_stop_charge"
  }
}

Input Schema

Name	Required	Description	Default
`vehicle_key`	Yes	Vehicle key (the `vehicleKey` from the vehicle-list tool). Not the VIN. Required: charging tools never default to the only vehicle.
`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.

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": "Vehicle key (the `vehicleKey` from the vehicle-list tool). Not the VIN. Required: charging tools never default to the only vehicle.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / vinKey

Removed value: -{
-  "description": "Vehicle key (the `vehicleKey` from the vehicle-list tool). Not the VIN.",
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[!-~]+$",
-  "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"
+}

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"

First observedv0.1.0Jul 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: documents the observed latency (~30-60s until evStatus.batteryCharge flips false), warns that the success status is not trustworthy, and explains the two-phase confirmation fallback where the first call makes NO network call. The idempotent/destructive hints are consistent with this narrative.

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-loaded with the action and endpoint, then layered verification and confirmation detail. Dense but every sentence carries new information; only slight length cost from the parenthetical about MCP_CONFIRM_MODE.

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?

No output schema exists, so the description must cover return behavior, and it does: it describes the phase-1 'confirmation-required' preview plus confirmToken and the eventual charging state change. An agent has everything needed to call and verify correctly.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters (vehicle_key, confirmToken) are already thoroughly documented in the schema. The description restates the confirmToken flow and the MCP_CONFIRM_MODE mechanism, which adds framing but little syntax the schema lacks; baseline 3 applies.

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?

States a specific verb+resource ('Ask the vehicle to stop charging') and even names the underlying endpoint (`evc/cancel`). It is unambiguously distinguishable from the sibling kia_start_charge / kia_start_climate tools.

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?

Gives explicit post-call guidance: verify with kia_vehicle_status instead of trusting the success status, and it spells out when the confirmation prompt applies and how the no-elicitation fallback works. It does not explicitly contrast with start_charge, but the operational context is clear enough to act on.

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

Deploy Server