Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_start_charge

Idempotent

Initiate remote charging for a plugged-in Kia EV, with a required confirmation and optional charge limit up to 100%.

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
vinKeyYesVehicle key (the `vehicleKey` from the vehicle-list tool). Not the VIN.
chargeRatioNoCharge up to this percentage, 10–100. Defaults to 100.
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. 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"
+}
  2. 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"
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses several critical behaviors: the call is a no-op on an unplugged car, the first call may make no network request and instead return a preview with confirmToken, a second call with that token is required, and the battery charge state can take 30–60 seconds to update. It also warns not to trust the success status, which is valuable operational context. No contradiction with the annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: purpose, expected behavior, prerequisite, verification instruction, and confirmation mechanics. It is front-loaded with the core action and each subsequent detail addresses a real operational risk or workflow requirement. There is no filler or redundant restatement of the tool name.

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?

Despite having no output schema, the description supplies the essential response-level information: a preview plus confirmToken on the fallback path, the observable success signal (evStatus.batteryCharge), the timing, and the need to verify with kia_vehicle_status. For a mutating, user-confirmation-gated tool, this is sufficient for an agent to select and invoke it correctly.

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?

The input schema already provides 100% parameter coverage with clear descriptions, so the baseline is 3. The description adds meaningful workflow semantics around confirmToken: it explains that the token comes from a phase-1 preview response, must be passed back only after explicit user approval, and only with the same arguments. This goes beyond the schema by connecting the parameters to the two-step confirmation behavior.

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 action ('Ask the vehicle to start charging') tied to a concrete endpoint (`evc/charge`), and it is clearly distinguishable from sibling tools like kia_stop_charge and kia_vehicle_status. It leaves no doubt about what resource is being acted on and what the intended outcome is.

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 gives strong contextual guidance: the car must be plugged in, otherwise the request is accepted but does nothing; the tool should not be trusted for confirmation, with kia_vehicle_status named as the verification path; and user confirmation is required first. It does not explicitly compare against alternatives like kia_stop_charge, but the constraints and workflow are clear enough for an agent to decide when to use it.

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