polestar-mcp

Get location

get_location

Read-only

Retrieve the last known position of your Polestar vehicle: latitude, longitude, altitude, heading, speed, and timestamp. Use it to confirm where your car was last seen.

Instructions

Last known position: latitude, longitude, altitude, heading, speed, with timestamp. (M2M endpoint: /v1/vehicles/{vin}/telemetry/location, scope pdp-telemetry/location).

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the upstream M2M endpoint and required OAuth scope, which is useful operational context, but does not disclose data freshness, rate limits, or other behavioral caveats.

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?

A single sentence front-loads the core result fields and places the endpoint/scope in a compact parenthetical. Every word earns its place; there is no redundancy or filler.

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?

For a zero-required-parameter read tool with rich schema documentation and an output schema, the description plus annotations are almost fully sufficient. The only meaningful gap is the absence of any guidance about when this tool should be preferred over sibling getters.

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?

The input schema describes all three parameters fully, including the VIN optionality rule and the raw payload redaction caveat. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 names a precise resource ('last known position') and enumerates the exact payload fields: latitude, longitude, altitude, heading, speed, and timestamp. This clearly distinguishes get_location from the other telemetry getters in the sibling list.

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

Usage Guidelines2/5

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

The description does not explain when to use this tool versus alternatives, nor does it give any exclusions, prerequisites, or conditional guidance. The endpoint and scope are informative context, but not usage direction.

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