openchargemap-mcp-server

openchargemap-mcp-server: get station

openchargemap_get_station

Read-onlyIdempotent

Get the full record for one Open Charge Map station by its numeric OCM ID. Returns every connection (type, level, power, current, quantity, per-connection status), the operator and network, usage and access restrictions (pay-at-location, membership, access key), the number of charge points, general comments, usage cost, the data provider, media, and verification recency. Set includeComments to also return community check-ins inline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Numeric OCM station ID (e.g. 145452).
`includeComments`	No	Include community check-ins and comments inline in the response. Adds payload but gives the real-world reliability signal alongside the registry status. Every comment on record comes back at once, unpaged — on a station with hundreds of check-ins that is a large response, so prefer openchargemap_get_station_comments, which returns them a page at a time.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`station`	No	The full station record.
`attribution`	No	Required CC BY 4.0 attribution to Open Charge Map contributors.
`reliabilityNote`	No	A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 20, 2026
- removedOutput schema / properties / station / properties / comments / items / properties / rating / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / comments / items / properties / rating / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / station / properties / connections / items / properties / amps / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / connections / items / properties / amps / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / station / properties / connections / items / properties / powerKW / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / connections / items / properties / powerKW / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / station / properties / connections / items / properties / quantity / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / connections / items / properties / quantity / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / station / properties / connections / items / properties / voltage / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / connections / items / properties / voltage / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / station / properties / dateLastStatusUpdate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / dateLastStatusUpdate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / station / properties / dateLastVerified / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / station / properties / dateLastVerified / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "station",
+      "attribution"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: OCM returned an empty result for the given numeric ID (HTTP 200 with []) — no such station. `upstream_unavailable`: OCM returned a non-2xx response or timed out. `auth_failed`: OCM returned HTTP 401 or 403 — the API key is missing or invalid. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "upstream_unavailable",
+            "auth_failed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "station",
-  "attribution"
-]

Changed1 schema field changedAug 6, 2026

changedInput schema / properties / includeComments / description

Previous value: -"Include community check-ins and comments inline in the response. Adds payload but gives the real-world reliability signal alongside the registry status. For comments alone, use openchargemap_get_station_comments."New value: +"Include community check-ins and comments inline in the response. Adds payload but gives the real-world reliability signal alongside the registry status. Every comment on record comes back at once, unpaged — on a station with hundreds of check-ins that is a large response, so prefer openchargemap_get_station_comments, which returns them a page at a time."

Changed5 schema fields changedAug 6, 2026

addedOutput schema / properties / station / properties / comments / items / properties / checkinStatus

Added value: +{
+  "description": "The visit outcome the driver recorded (e.g. \"Charged Successfully\", \"Failed to Charge (Equipment Not Operational)\"). Carries the result on check-ins that have no comment text. Absent when the visitor recorded no outcome.",
+  "type": "string"
+}

addedOutput schema / properties / station / properties / comments / items / properties / checkinStatusId

Added value: +{
+  "description": "Numeric ID of the check-in outcome, stable across renames of its title.",
+  "type": "number"
+}

addedOutput schema / properties / station / properties / comments / items / properties / checkinStatusIsPositive

Added value: +{
+  "description": "Whether the registry classes this outcome as a good visit. Absent when the outcome carries no verdict either way (e.g. \"Did Not Visit Location\") or when none was recorded.",
+  "type": "boolean"
+}

addedOutput schema / properties / station / properties / comments / items / properties / relatedUrl

Added value: +{
+  "description": "Link the commenter attached. Absent when none was given.",
+  "type": "string"
+}

addedOutput schema / properties / station / properties / statusTypeId

Added value: +{
+  "description": "Registry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record.",
+  "type": "number"
+}

Changed6 schema fields changedJul 4, 2026

changedInput schema / properties / id / description

Previous value: -"Numeric OCM station ID (e.g. 145452). Obtain one from openchargemap_find_stations. Note: UUID lookup is not supported by the OCM API."New value: +"Numeric OCM station ID (e.g. 145452)."

changedOutput schema / properties / reliabilityNote / description

Previous value: -"Server-computed caveat when registry status and recency suggest the listing may not reflect reality (plain prose from observable facts; no synthetic score). Omitted when status is fresh and uncontested."New value: +"A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag."

changedOutput schema / properties / station / properties / distanceUnit / description

Previous value: -"Unit of the distance value (normalized from the OCM integer enum: 1=KM, 2=Miles)."New value: +"Unit of the distance value."

changedOutput schema / properties / station / properties / id / description

Previous value: -"OCM station ID. Pass to openchargemap_get_station or openchargemap_get_station_comments."New value: +"OCM station ID."

changedOutput schema / properties / station / properties / isOperational / description

Previous value: -"Whether the registry marks the status operational. Absent (not null) when StatusType is \"Unknown\" (ID=0) — OCM omits the flag then. A true value can still mask a broken charger — corroborate with comments and dateLastVerified."New value: +"Whether the registry marks the status operational. Absent when the operational state is unknown. A true value can still mask a broken charger — corroborate with comments and dateLastVerified."

changedOutput schema / properties / station / properties / isRecentlyVerified / description

Previous value: -"OCM flag: whether the listing was verified recently."New value: +"Whether the listing was verified recently."

First observedJun 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses key behavioral traits: includeComments returns every unpaged comment at once, potentially producing a large payload, and the comments are described as a reliability signal alongside registry status. No contradictions with annotations are present.

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?

Three dense sentences with no filler. The core purpose is front-loaded, followed by the return contents and the single behavioral caveat. Every sentence earns its place.

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?

With a full output schema, complete input schema, annotations for safety/idempotency, and a description covering the large-response caveat and sibling alternative, the agent has everything needed to decide when and how to call this tool.

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?

Schema coverage is 100%, so the baseline is 3. The description adds real value by explaining the trade-off of includeComments (inline reliability signal vs. large unpaged response) and explicitly recommending the sibling for paged access, going beyond the schema's default/boolean description.

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?

Uses a specific verb and resource: 'Get the full record for one Open Charge Map station by its numeric OCM ID.' It clearly distinguishes this from discovering stations (find_stations) and from paged comment retrieval (get_station_comments).

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 tells the agent to prefer openchargemap_get_station_comments when community comments should be returned one page at a time, an explicit alternative. It could more explicitly contrast with openchargemap_find_stations for cases where the ID is unknown, but the ID-based phrasing implies the boundary.

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

All openchargemap-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.