Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_start_charge

Idempotent

Ask the vehicle to start charging (evc/charge). Verified against a plugged-in vehicle: evStatus.batteryCharge goes true within ~30-60s.

Instructions

Ask the vehicle to start charging (evc/charge). Verified against a plugged-in vehicle: evStatus.batteryCharge goes true within ~30-60s. Requires the car to be plugged in — on an unplugged car Kia still accepts the request and nothing happens. 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chargeRatioNoCharge up to this percentage, 10–100. Defaults to 100.
vehicle_keyYesVehicle key (the `vehicleKey` from the vehicle-list tool). Not the VIN. Required: charging tools never default to the only vehicle.
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": "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"
+]
  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. 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"
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover safety (non-destructive, idempotent) but the description adds high-value behavior the annotations can't: silent no-op on unplugged vehicles, ~30-60s latency before evStatus.batteryCharge flips, and unreliable success status. It also explains the confirmation flow (preview + confirmToken, or elicitation). Minor gap: doesn't state auth/session requirements beyond the confirmation note.

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 purpose and the API endpoint, then verification conditions and confirmation flow. Dense but well-organized; the confirmation paragraph is slightly long but justified by a non-obvious two-phase behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the mutation's non-obvious risks (silent no-op, flaky success signal) and the async confirmation mechanism, which is the main thing an agent could get wrong. A note on auth/session prerequisites would complete it, but it is otherwise complete for a 3-param write tool with no output schema.

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%, so vehicle_key, chargeRatio (10-100, default 100), and confirmToken are already fully documented in the schema. The description mentions confirmToken behavior, which is the schema's own text, so it adds no new semantic detail. Baseline 3.

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?

Specific verb+resource ('start charging') with the underlying API endpoint named (evc/charge), which distinguishes it cleanly from kia_stop_charge and kia_set_charge_limits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit prerequisites (car must be plugged in, and that an unplugged car silently no-ops), plus explicit routing: confirm via kia_vehicle_status rather than trusting success.

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