polestar-mcp

List data domains

list_domains

Read-only

List all valid data domains with their endpoints, OAuth scopes, and tool names to query your Polestar vehicle without encountering unknown-domain 404 errors.

Instructions

Every domain this server reads, with its endpoint, OAuth scope and tool name. Answer from here rather than guessing a domain name: an unknown domain is a 404 VALIDATION_RESOURCE_NOT_FOUND from the API, which is a different thing from a vehicle reporting no data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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

Behavior4/5

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

Annotations already mark this as read-only and not open-world, and the description reinforces that by saying 'Every domain this server reads.' It adds valuable behavioral context about the 404 error semantics and the distinction from missing vehicle data, which goes beyond the annotations without contradicting them.

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, purposeful sentences. The first states exactly what is returned, and the second gives actionable guidance. No filler or redundancy.

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 parameterless, read-only listing tool with an output schema present, the description fully covers what the tool does, what it returns, and when to use it. The error-semantics note adds important operational context that the schema and annotations alone would not provide.

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?

The tool has zero parameters, so description-level parameter semantics are largely irrelevant. The baseline of 4 applies because there is nothing for the description to clarify about inputs.

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 lists every domain the server reads, with endpoint, OAuth scope, and tool name. This distinguishes it from siblings like list_vehicles and the get_* tools, which retrieve vehicle-specific data rather than a catalog of domains.

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?

The description explicitly tells the agent to consult this tool rather than guessing a domain name. It also clarifies the difference between an unknown domain returning a 404 VALIDATION_RESOURCE_NOT_FOUND and a vehicle reporting no data, helping the agent diagnose errors correctly.

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