Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_set_charge_limits

Idempotent

Set the target state of charge per plug type (evc/sts). Verified against a real vehicle. The write is checked: afterwards the targets are re-read from evc/gts and compared, and the result reports whether the change actually landed.

Instructions

Set the target state of charge per plug type (evc/sts). Verified against a real vehicle. The write is checked: afterwards the targets are re-read from evc/gts and compared, and the result reports whether the change actually landed. Send BOTH plug types — the list replaces the stored one, so omitting an entry drops that target. 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). The preview step makes no call at all, not even the baseline read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verifyNoRe-read evc/gts afterwards to check the change landed. Defaults to true.
targetsYesOne entry per plug type. Read the current targets first and change only what you mean to.
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",
-  "targets"
-]New value: +[
+  "vehicle_key",
+  "targets"
+]
  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. Changed1 schema field changedv0.6.1
    • changedInput schema / properties / targets / items / properties / plugType / description
      Previous value: -"Plug type, 0 or 1 — one entry per plug type (AC and DC). Which number is which is NOT verified: read the current targets first and mirror the plugType values it returns."New value: +"Plug type: 1 = AC, 0 = DC per the open-source Kia client, though this server has not confirmed it against a vehicle (both targets were set and restored together during verification, so the two were never distinguished). Safest usage is unchanged: read the current targets first and mirror the plugType values it returns. Note evc/sts REPLACES the list, so send an entry for BOTH plug types."
  5. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, but the description adds substantial context beyond them: the write is verified by re-reading evc/gts and reporting whether it landed, the list REPLACES stored state (a destructive-in-effect REPLACE semantic that annotations don't capture), and the preview phase makes no network call at all. The confirmation behavior is fully disclosed.

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 core purpose and the verified-write fact, then the mutation-vs-replace warning, then the confirmation flow. Every sentence earns its place, though the confirmation section is dense and could be more skimmable.

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?

Given a mutation tool with no output schema and complex two-phase confirmation, the description covers everything an agent needs: scope, replace semantics, verification, and the exact confirmation protocol including the preview/confirmToken fallback. Nothing critical 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. The description adds value by explaining the REPLACE semantics of the targets list and the two-phase confirmToken flow, which are not fully conveyed by the schema alone. It doesn't restate parameter syntax (the schema handles that), so it doesn't reach 5.

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 precise verb+resource: 'Set the target state of charge per plug type'. It also ties the write to the underlying evc/sts path, which distinguishes it from the read-side sibling kia_charge_targets (which reads evc/gts). An agent can differentiate this from kia_charge_targets without opening either schema.

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 guidance on when and how: 'Send BOTH plug types — the list replaces the stored one, so omitting an entry drops that target.' It also delineates the confirmation flow (client prompt vs two-step confirmToken fallback) and warns that the first call makes no network call. This is unusually thorough routing information.

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