Skip to main content
Glama

openchargemap-mcp-server

by io.github.cyanheads

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
NameRequiredDescriptionDefault
idYesNumeric OCM station ID (e.g. 145452).
includeCommentsNoInclude 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
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
stationNoThe full station record.
attributionNoRequired CC BY 4.0 attribution to Open Charge Map contributors.
reliabilityNoteNoA 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. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • 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"
-]
  2. Changed1 schema field changed
    • 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."
  3. Changed5 schema fields changed
    • 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"
+}
  4. Changed6 schema fields changed
    • 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."
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds behavioral context beyond annotations: it discloses that includeComments returns all comments unpaged and can produce a large response, explicitly warning about payload size and recommending the paginated alternative. This extra disclosure of a non-obvious behavior (unpaged, potentially huge) goes beyond the annotations and is valuable for the agent's decision-making. No contradiction with annotations detected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with its purpose, then lists the returned fields concisely, and ends with the optional parameter note. It's informational without redundancy, though the enumeration of field groups is somewhat lengthy. Every sentence contributes to understanding what the tool returns or how to use it. It's structured well, not verbose to the point of distraction, so a 4 is appropriate.

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 single-station retrieval tool with a rich output schema (has output schema: true), the description sufficiently explains what is returned (full record fields) and the optional comment inclusion behavior, including the warning about payload size and the alternative. It covers all key aspects a caller needs: identifier, optional flag, and behavioral nuance. The presence of an output schema means return structure details are not the description's job. No significant missing pieces for this moderate-complexity tool.

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?

Schema description coverage is 100% — both 'id' and 'includeComments' have clear descriptions in the input schema. The description text itself reiterates the includeComments behavior ('Set includeComments to also return community check-ins inline') but adds no new semantics beyond the schema, which already explains the unpaged nature and suggests the sibling tool. Since the schema fully covers parameter meaning, the baseline of 3 applies; the description provides no additional value over schema.

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?

Description uses the specific verb 'get' with a clear resource ('full record for one Open Charge Map station') and a precise identifier ('numeric OCM ID'). It enumerates exactly what is returned (connections, operator, access restrictions, cost, etc.), distinguishing it from siblings like openchargemap_get_station_comments (which focuses on comments) and openchargemap_find_stations (search). The purpose is unambiguous and fully differentiated.

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 and includeComments parameter explicitly state when to use the alternative tool: 'prefer openchargemap_get_station_comments, which returns them a page at a time.' It effectively tells the agent that for a full station record, this tool is appropriate, and for paginated comments, use the sibling. However, it does not explicitly contrast with find_stations (search vs single-record) beyond the obvious purpose, which is implicitly clear from the purpose statement. Still, the guidance for the main alternative is explicit, earning a high score but not perfect.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a distinct role: discovery (find_stations), retrieval (get_station), community feedback (get_station_comments), and reference lookup (lookup_reference). No two tools overlap in purpose, and the descriptions reinforce their boundaries.

Naming Consistency5/5

All tool names share the 'openchargemap_' prefix followed by a clear verb_noun pattern (find_stations, get_station, get_station_comments, lookup_reference). The naming is uniform and predictive, making it easy for an agent to infer function.

Tool Count5/5

With 4 tools, the server is focused and well-scoped for a read-only EV charging station registry. Each tool serves an essential query need (search, detail, comments, reference data) without unnecessary clutter.

Completeness5/5

The tool set covers the full lifecycle of querying station data: resolving reference IDs via lookup_reference, searching with filters, retrieving detailed records, and accessing community feedback. This is complete for the stated purpose, with no obvious dead ends.

Resources