polestar-mcp

Get is-at-charge-location

get_is_at_charge_location

Read-only

Check if your Polestar vehicle is currently parked at a saved charging location. Get a clear yes/no answer, with handling for unsupported data.

Instructions

Whether the vehicle is currently at a saved charge location. Often unsupported on a vehicle (returns DATA_NOT_AVAILABLE). (M2M endpoint: /v1/vehicles/{vin}/charging/is-at-charge-location, scope pdp-charging/isAtChargeLocation).

Input Schema

TableJSON Schema

Name	Required	Description
`raw`	No	Return the full raw API payload instead of (or after) the humanized summary. Unchanged upstream content: it carries the VIN even when POLESTAR_REDACT_VIN is on.
`vin`	No	Vehicle Identification Number. Optional when the credential has exactly one vehicle, omit it and the only vehicle is used.
`delegated_account_id`	No	Third-party credentials only: read the shared vehicles of this account for this call. Must be listed in POLESTAR_DELEGATED_ACCOUNT_IDS.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	False when the call produced no data.
`vin`	No	Vehicle the result is about, masked when POLESTAR_REDACT_VIN is on.
`code`	No	Machine-readable error code when ok is false.
`data`	No	Structured payload; shape documented per tool.
`hint`	No	Actionable guidance when ok is false.
`tool`	No	Tool that produced this result.
`message`	Yes	Result text, identical to the content block.
`requestId`	No	Upstream request id, the handle support needs.
`ageSeconds`	No	Staleness of the underlying telemetry.
`httpStatus`	No	Upstream HTTP status when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 19, 2026

TDQS

A4.3/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, but the description adds valuable behavioral context by noting the tool often returns DATA_NOT_AVAILABLE on unsupported vehicles. It also provides the endpoint and scope, which helps with debugging and authorization.

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 a single, clear sentence with a parenthetical technical note. It is front-loaded and contains no fluff, making it easy for an agent to parse quickly.

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?

For a simple getter with all-optional parameters, an output schema, and annotations covering read-only and open-world behavior, the description covers the key edge case (DATA_NOT_AVAILABLE) and provides the endpoint. Nothing essential is missing for correct invocation.

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%, so the parameters are fully documented in the schema. The description adds no additional parameter-level meaning, so it meets the baseline for high coverage without extra value.

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 clearly states the tool checks whether the vehicle is currently at a saved charge location, using a specific verb and resource. It also distinguishes itself from sibling tools like get_charge_locations (which lists saved locations) by focusing on the current state.

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?

The purpose is clear enough that an agent can infer when to use it (checking current location vs. listing saved locations). However, it does not explicitly name alternatives or provide conditions, leaving slight room for ambiguity in tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.