polestar-mcp

Get amp-limit

get_amp_limit

Read-only

Retrieve your Polestar's configured AC charging current limit in amps, including its source and last update, plus any pending amp limit change awaiting car confirmation.

Instructions

Configured maximum AC charging current (amps) with its source and last update, plus pendingAmpLimit when a change is recorded but the car has not confirmed it. Measured live. (M2M endpoint: /v1/vehicles/{vin}/charging/amp-limit, scope pdp-charging/ampLimit).

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

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description adds meaningful behavior: the value is measured live, includes source and last update, and pendingAmpLimit appears only when a change is recorded but unconfirmed by the car. This helps the agent interpret freshness and pending state correctly.

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?

Two dense, information-rich sentences with no filler. The core semantics are front-loaded, and the endpoint/scope parenthetical is compact and useful for authorization context.

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 zero-required-parameter read with an output schema, the description covers the core result, live behavior, pending state, endpoint, and authorization scope. Nothing critical for correct invocation or interpretation 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?

The input schema already documents all three parameters with 100% coverage, including the VIN optionality and the raw flag's warning about carrying the VIN despite redaction. The description itself adds no parameter-level meaning, so the baseline 3 applies.

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 identifies exactly what is returned: the configured maximum AC charging current in amps, its source, last update, and pendingAmpLimit when the car has not yet confirmed a change. This clearly distinguishes it from sibling tools like get_target_soc and get_charging_estimate.

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 description gives clear context: it is the configured amp limit, measured live, so the agent understands when to use it for live charging-current-limit reads. It does not explicitly name alternatives or exclusions, but the stated purpose makes the usage straightforward.

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