Skip to main content
Glama
Sign In
Kia Access MCP

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_charge_targets

Read-only

Read the EV charge targets (evc/gts): the target state of charge per plug type (one entry for AC, one for DC). Verified live against a real vehicle. Read-only — makes no changes.

Instructions

Read the EV charge targets (evc/gts): the target state of charge per plug type (one entry for AC, one for DC). Verified live against a real vehicle. Read-only — makes no changes.

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_charge_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicle_keyYesVehicle key (the `vehicleKey` from the vehicle-list tool). Not the VIN. Required: charging tools never default to the only vehicle.

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. 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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description usefully reinforces it ('makes no changes') and adds real context the annotations cannot — that the values are verified against a live vehicle and that the payload is one entry per plug type (AC/DC). It does not mention auth/session prerequisites, but the added return-shape and live-verification detail is meaningful.

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?

Three short clauses, front-loaded with the verb and resource before the payload detail and the read-only reassurance. No filler sentences; every clause carries information.

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?

With no output schema, the description partially compensates by describing the return contents (one entry per plug type for AC/DC). Combined with annotations covering read-only/open-world and a fully documented single parameter, an agent has enough to call it correctly, though field-level return detail and session/auth behavior remain implicit.

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% — vehicle_key is fully documented in the schema, including the crucial 'not the VIN' and 'never defaults to the only vehicle' notes. The description adds nothing about parameters, which is the expected baseline when the schema does the work.

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 and resource ('Read the EV charge targets') and names the underlying endpoint (`evc/gts`), then specifies exactly what is returned: target state of charge per plug type, one entry for AC and one for DC. This is clearly distinguishable from the mutation sibling kia_set_charge_limits and from the broader status tools.

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

Usage Guidelines3/5

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

Usage is implied by the framing ('Read the EV charge targets') and the closer 'Read-only — makes no changes' signals it is the inspection half of the charge-limit pair. However, it never explicitly says when to reach for this versus kia_set_charge_limits or kia_session_status, and gives no prerequisites beyond the schema.

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