Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_vehicle_status

Read-onlyIdempotent

Read the vehicle's CACHED status (cmm/gvi): door lock, ignition, and the remote-climate block. Fast, but it reports whatever the telematics unit last uploaded — use kia_refresh_status first when freshness matters.

Instructions

Read the vehicle's CACHED status (cmm/gvi): door lock, ignition, and the remote-climate block. Fast, but it reports whatever the telematics unit last uploaded — use kia_refresh_status first when freshness matters. Requested with airTempRange/seatHeatCoolOption = "1" so the nested climate object is present; when it is still absent the result says so rather than reporting climate as off. Note ign3 (not engine) is the ignition on an EV, and syncDate advances on every read, so it never proves anything changed. Per-seat heat/vent state is reported under climate.seats as the RAW numbers Kia sends: the heatVentType/heatVentLevel encoding is UNVERIFIED, so do not tell the user a seat is heating, ventilating or off based on them. An absent seat block means this read carried no seat data — it does NOT mean the car lacks heated seats, which this server cannot currently determine. Pass include_raw for the untrimmed status block (battery/EV detail, doors, tyres, …).

Input Schema

NameRequiredDescriptionDefault
include_rawNoInclude the full vehicleStatus block as `raw` (default false).
vehicle_keyNovehicleKey from kia_list_vehicles. Optional: defaults to the only vehicle when the account has exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.5
    • addedInput schema / properties / vehicle_key / allOf
      Added value: +[
+  {
+    "pattern": "^[^/?#\\s]+$"
+  },
+  {
+    "pattern": "^[!-~]+$"
+  }
+]
    • addedInput schema / properties / vehicle_key / maxLength
      Added value: +200
    • removedInput schema / properties / vehicle_key / pattern
      Removed value: -"^[^/?#\\s]+$"
  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.8/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/openWorld, but the description goes far beyond: cache-staleness semantics, why climate may be absent rather than off, EV ignition naming (ign3 vs engine), the fact that syncDate never proves change, and an explicit warning that seat heat/vent encoding is UNVERIFIED. This is unusually rich operational context that prevents wrong agent inferences.

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?

Dense but front-loaded: purpose and the freshness caveat come first, then the domain caveats. Every sentence carries distinct operational value with no filler, though the paragraph is long and could be split for scanability.

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?

With no output schema and a complex automotive domain, the description compensates thoroughly, explaining return-field semantics (climate, ign3, syncDate, climate.seats) and their absence conditions. An agent has everything needed to call it and interpret results 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?

Schema coverage is 100%, setting a baseline of 3. The description earns above-baseline credit by expanding what include_raw actually returns (battery/EV detail, doors, tyres) and by noting vehicle_key can be passed implicitly, adding meaning beyond the terse schema strings.

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 ('Read the vehicle's CACHED status') and enumerates the exact surface (door lock, ignition, remote-climate block). It explicitly distinguishes itself from the sibling kia_refresh_status, so an agent can route without opening a 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?

Gives an explicit when-to-use ('Fast') alongside the condition that selects the alternative ('use kia_refresh_status first when freshness matters'). The stale-data caveat functions as a clear when-not, and the include_raw hint maps to a usage decision.

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