Charging stations

Get detailed private information about a charge station, scoped to the caller. Returns account, billing plan, location including who is reimbursed for sessions and who is invoiced for the subscription, whether it is published publicly, the installer or maintenance account, connector specifications, active issues, and the per-connector OCPI tariff as pushed to roaming partners. Requires a verified user attached to the current session; if the session has no verified user yet, ask for their email and use the customer-request-verification and customer-verify flow. Scoped to the caller: a station at a location linked to them, or any station on the account for a caller with account-level charge-point read access, except a colleague's employee-reimburse (home) charge point, which is never shown. Anything out of scope is reported as not found, the same as a station that does not exist. The `identifier` must be precise (typically the `normalizedEvseId` returned by charge-points-find). If the user gave a description, partial id, or noisy voice input, call charge-points-find first to resolve it.

Disambiguate a charge station from fuzzy, partial, or voice-shaped input. Accepts free text (address, city, vendor, station name) or a noisy id (e.g. "NL*EFL*EV2985978*C1" or "AC 10729 126"). Returns a list of candidate stations with their canonical `normalizedEvseId`. The caller must pass that `normalizedEvseId` back into charge-points-status / -details / -reboot / -unlock to act on a station; those tools do not accept fuzzy input. No authentication required.

Reboot a charge station with a built-in safety check. Before sending the reset the tool verifies, server-side, that the station is online, that no other driver is charging on it (on multi-connector stations), and that the customer's most recent attempt to start a session was not rejected for token-level reasons. It reboots the station only when those checks pass. The response is shaped as: `reset` (boolean, whether the reset actually ran), `reason` (the human-readable explanation to relay to the customer), and two independent agent hints: `needConnector` (ask the customer which connector they are using, left is 1, right is 2, and call again with connectorId) and `escalate` (the reset will not help, hand off to human support). Also returns `lastSessionAttempt` mirroring the charge-points-status tool, so the agent has context for whatever it tells the customer. Does not require authentication, but a verified session lets the tool tell the customer's own token failures apart from someone else's. The `identifier` must be precise (typically the `normalizedEvseId` returned by charge-points-find); if the user gave a description, partial id, or noisy voice input, call charge-points-find first to resolve it.

Lists charging sessions that took place on the account's charge points (the operator view): who charged, energy delivered, duration and revenue. Returns live (in-progress) and recent (completed) sessions. Callers with account-level charge-point session read access see all the account's charge-point sessions; other callers see only sessions at their own reimbursement locations (e.g. a home charge point). For sessions the account's users ran at other operators, use charging-card-sessions.

Gather the facts needed to reason about a charge station: connectivity, per-connector status, active issues, tariff, last successful session per connector, and the most recent token-authorisation attempt. The per-connector tariff is formatted according to the OCPI standard.Use this to answer questions about whether a station is online, available, or experiencing problems, and to understand why a customer cannot charge. Returns non-sensitive information; no authentication required. When a verified caller is attached, the most-recent-attempt section is enriched to indicate whether the attempt was made with one of the caller's own tokens. When the most recent attempt was refused because the token already had a session running elsewhere (outcome `ConcurrentTx`), `blockingSessionId` names that session, so the customer can be told what is holding their card and a human picking the case up does not have to search for it. Calling this is NEVER required before charge-points-reboot: the reboot tool runs the same checks internally as a safety gate. The `identifier` must be precise (typically the `normalizedEvseId` returned by charge-points-find); if the user gave a description, partial id, or noisy voice input, call charge-points-find first to resolve it.

Returns an account-wide charge-point summary: how many charge points and locations the account operates, sessions currently active on them, and current-month CPO session totals (energy, duration), plus a list of the account's charge points (up to 50). Callers with account-level charge-point read access see the list; other callers see the aggregate stats only. For a single charge point's live status or owner detail use charge-points-status / -details; to look one up use charge-points-find.

Unlock a connector on a charge station to release a stuck cable. Use when a customer reports they cannot unplug their vehicle. Does not require authentication; intended as a self-service action for the person standing at the station. The `identifier` must be precise (typically the `normalizedEvseId` returned by charge-points-find). If the user gave a description, partial id, or noisy voice input, call charge-points-find first to resolve it.