Skip to main content
Glama
chrischall

Kia Access MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kia_vehicle_location

Read-onlyIdempotent

The vehicle's last known location, from the location block of the cached cmm/gvi read. This is where the telematics unit last reported being, not a live GPS fix — run kia_refresh_status first for a recent one.

Instructions

The vehicle's last known location, from the location block of the cached cmm/gvi read. This is where the telematics unit last reported being, not a live GPS fix — run kia_refresh_status first for a recent one. Latitude/longitude and a map link are derived when the block carries coord.lat/coord.lon; otherwise the raw block is returned as-is (its exact field names are not verified).

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld/idempotent, but the description adds real behavioral context beyond them: data provenance (cached cmm/gvi read), staleness, the conditional derivation path when coord.lat/coord.lon exist, the raw-block fallback, and an honest caveat that the raw block's field names are unverified.

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?

Three dense sentences with no filler, and the most decision-relevant fact (cached, not live) is front-loaded. It is a bit long for a one-parameter read tool, but every clause adds distinct information.

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?

No output schema exists, so the description must explain return values - and it does, covering both the derived lat/lon plus map link case and the raw-block fallback, including the uncertainty about field names. Nothing an agent needs to interpret the result is missing.

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% and vehicle_key is fully documented in the schema (including the single-vehicle default), so the description carries no additional parameter information. Baseline 3 applies when the schema does the heavy lifting.

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 - returns the vehicle's last known location - and immediately scopes it as coming from the cached cmm/gvi read rather than a live GPS fix. This distinguishes it from kia_refresh_status and the other status siblings without needing to open any 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?

Explicitly names the alternative (kia_refresh_status) and the condition that selects it ('run kia_refresh_status first for a recent one'), plus the freshness caveat that defines when this cached tool is appropriate. An agent has a clear routing rule.

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