Skip to main content
Glama

openchargemap-mcp-server: find stations

openchargemap_find_stations
Read-only

Find EV charging stations from the global Open Charge Map registry near a point or within a bounding box. Provide either a center (latitude + longitude + distance) or a boundingbox; optionally scope to a country with countrycode. This tool is coordinate-native and does not geocode place names — resolve a place like "Ballard, Seattle" to coordinates with openstreetmap_geocode first, then pass them here. Filter by connector type, minimum power (kW), operator/network, usage type (public/free/membership), charge level, operational status, and minimum charge points. Filter IDs are integers — resolve a connector or network name to its ID with openchargemap_lookup_reference (e.g. "CCS" -> 33). Each result includes title, address, distance from the search point, connections (type, power, count), operator, access rules, registry operational status, and the last-verified date. Results come back one page at a time: when a page reports truncated, repeat the same search with the reported nextOffset to read the next one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoMatching stations to skip before the returned page, for reading past a truncated result. Repeat the same search with the nextOffset value the previous call reported. One search reaches at most 500 stations, so 499 is the deepest offset that can return one — narrow the area or add filters to reach stations beyond that. Ordering is by distance and stable, but Open Charge Map is edited continuously, so a station added or removed between pages can shift what a later offset lands on.
levelidNoCharge level ID (1=Low <2kW, 2=Medium >2kW, 3=High >40kW/fast). Array OR-matched. Use 3 as a coarse "fast charging only" filter when a specific connector is not required.
distanceNoSearch radius from the center point, in the unit given by distanceUnit (default km). Max 500. Keep small (5-25) for dense urban areas; widen for rural coverage.
latitudeNoCenter latitude (WGS84 decimal degrees). Use with longitude + distance for a radius search. Resolve place names via openstreetmap_geocode first.
longitudeNoCenter longitude (WGS84 decimal degrees). Use with latitude + distance for a radius search.
maxresultsNoMaximum stations to return, ordered by distance from the search point. Max 200.
minpowerkwNoMinimum charging power in kW across any connection at the station. Use ~50 for DC fast charging, ~150 for high-power DC. Stations whose fastest connection is below this are excluded.
operatoridNoOperator/network ID, or array of IDs (OR-matched). Resolve a network name with openchargemap_lookup_reference (category "operators") — e.g. "Tesla", "ChargePoint".
boundingboxNoBounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance — sending a boundingbox alongside a latitude or a longitude is rejected, not resolved in favour of one of them.
countrycodeNoRestrict to one country by ISO 3166-1 alpha-2 code (e.g. "US", "FR", "GB"). Omit for a global search. The server is global by default — there is no implicit country.
usagetypeidNoUsage/access type ID, or array (OR-matched). Resolve via openchargemap_lookup_reference (category "usagetypes") — e.g. Public=1, Public-Pay At Location=5, Public-Membership Required=4.
distanceUnitNoUnit for the distance parameter and the returned distance values.KM
statustypeidNoRegistry operational-status ID, or array (OR-matched). Resolve via openchargemap_lookup_reference (category "statustypes"). NOTE: registry status is operator-reported and can be stale — combine with dateLastVerified and openchargemap_get_station_comments to judge real-world reliability, do not treat it as ground truth.
minchargepointsNoMinimum number of charge points (stalls) at the station. Filters out single-point locations when you need a station likely to have an open stall.
connectiontypeidNoConnector type ID, or an array of IDs (OR-matched). Resolve names with openchargemap_lookup_reference — e.g. CCS (Type 2)=33, CHAdeMO=2, NACS/Tesla Supercharger=27, Type 2 socket=25, Type 1/J1772=1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe maxresults cap that was applied.
errorNoPresent when the call failed. Absent on success.
shownNoStations in the returned page.
noticeNoHow to reach the stations this page left out, or why it came back empty.
stationsNoMatching stations, ordered by distance from the search point.
truncatedNoTrue when matching stations were left out of the returned page.
nextOffsetNoThe offset to pass on an otherwise identical call to read the next page. Absent when nothing further was retrieved.
totalCountNoMatching stations this search retrieved, before the offset/maxresults page was taken. Open Charge Map publishes no match total and one search can only retrieve so deep, so this is exact only when the search reached the end of what Open Charge Map holds for the area — otherwise it is a floor that rises as deeper pages are read. The notice says which of the two applies.
attributionNoRequired attribution to Open Charge Map contributors under CC BY 4.0.
searchSummaryNoHuman-readable echo of the resolved search: location mode, scope, and active filters as the server applied them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedOutput schema / properties / stations / items / properties / connections / items / properties / amps / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / stations / items / properties / connections / items / properties / amps / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / stations / items / properties / connections / items / properties / powerKW / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / stations / items / properties / connections / items / properties / powerKW / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / stations / items / properties / connections / items / properties / quantity / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / stations / items / properties / connections / items / properties / quantity / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / stations / items / properties / connections / items / properties / voltage / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / stations / items / properties / connections / items / properties / voltage / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / stations / items / properties / dateLastVerified / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / stations / items / properties / dateLastVerified / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. 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": [
      +      "stations",
      +      "searchSummary",
      +      "attribution",
      +      "totalCount"
      +    ]
      +  },
      +  {
      +    "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: `invalid_location`: No search area was provided; or only one half of a center arrived; or a boundingbox arrived alongside a latitude or a longitude. `no_stations`: Open Charge Map holds no station for the search area and filters — either it returned nothing at all, or every station it returned was ruled out and there were no further candidates. `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": [
      +            "invalid_location",
      +            "no_stations",
      +            "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: -[
      -  "stations",
      -  "searchSummary",
      -  "attribution",
      -  "totalCount"
      -]
  3. Changed7 schema fields changed
    • changedInput schema / properties / boundingbox / description
      Previous value: -"Bounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance."New value: +"Bounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance — sending a boundingbox alongside a latitude or a longitude is rejected, not resolved in favour of one of them."
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Matching stations to skip before the returned page, for reading past a truncated result. Repeat the same search with the nextOffset value the previous call reported. One search reaches at most 500 stations, so 499 is the deepest offset that can return one — narrow the area or add filters to reach stations beyond that. Ordering is by distance and stable, but Open Charge Map is edited continuously, so a station added or removed between pages can shift what a later offset lands on.",
      +  "maximum": 499,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "The offset to pass on an otherwise identical call to read the next page. Absent when nothing further was retrieved.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "How to reach the stations this page left out, or why it came back empty.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / shown / description
      Previous value: -"Number of stations returned when the cap was hit."New value: +"Stations in the returned page."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Number of stations returned."New value: +"Matching stations this search retrieved, before the offset/maxresults page was taken. Open Charge Map publishes no match total and one search can only retrieve so deep, so this is exact only when the search reached the end of what Open Charge Map holds for the area — otherwise it is a floor that rises as deeper pages are read. The notice says which of the two applies."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when results were capped at maxresults."New value: +"True when matching stations were left out of the returned page."
  4. Changed6 schema fields changed
    • changedInput schema / properties / connectiontypeid / anyOf
      Previous value: -[
      -  {
      -    "description": "A single reference ID.",
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "description": "Several reference IDs, OR-matched.",
      -    "items": {
      -      "description": "A reference ID.",
      -      "exclusiveMinimum": 0,
      -      "maximum": 9007199254740991,
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "description": "A single reference ID.",
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "description": "Several reference IDs, OR-matched. At least one.",
      +    "items": {
      +      "description": "A reference ID.",
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxItems": 10,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / levelid / anyOf
      Previous value: -[
      -  {
      -    "description": "A single reference ID.",
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "description": "Several reference IDs, OR-matched.",
      -    "items": {
      -      "description": "A reference ID.",
      -      "exclusiveMinimum": 0,
      -      "maximum": 9007199254740991,
      -      "type": "integer"
      -    },
      -    "maxItems": 3,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "description": "A single reference ID.",
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "description": "Several reference IDs, OR-matched. At least one.",
      +    "items": {
      +      "description": "A reference ID.",
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxItems": 3,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / operatorid / anyOf
      Previous value: -[
      -  {
      -    "description": "A single reference ID.",
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "description": "Several reference IDs, OR-matched.",
      -    "items": {
      -      "description": "A reference ID.",
      -      "exclusiveMinimum": 0,
      -      "maximum": 9007199254740991,
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "description": "A single reference ID.",
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "description": "Several reference IDs, OR-matched. At least one.",
      +    "items": {
      +      "description": "A reference ID.",
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxItems": 10,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / statustypeid / anyOf
      Previous value: -[
      -  {
      -    "description": "A single reference ID.",
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "description": "Several reference IDs, OR-matched.",
      -    "items": {
      -      "description": "A reference ID.",
      -      "exclusiveMinimum": 0,
      -      "maximum": 9007199254740991,
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "description": "A single reference ID.",
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "description": "Several reference IDs, OR-matched. At least one.",
      +    "items": {
      +      "description": "A reference ID.",
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxItems": 10,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / usagetypeid / anyOf
      Previous value: -[
      -  {
      -    "description": "A single reference ID.",
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "description": "Several reference IDs, OR-matched.",
      -    "items": {
      -      "description": "A reference ID.",
      -      "exclusiveMinimum": 0,
      -      "maximum": 9007199254740991,
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "description": "A single reference ID.",
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "description": "Several reference IDs, OR-matched. At least one.",
      +    "items": {
      +      "description": "A reference ID.",
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxItems": 10,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • addedOutput schema / properties / stations / items / 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"
      +}
  5. Changed5 schema fields changed
    • changedInput schema / properties / maxresults / description
      Previous value: -"Maximum stations to return, ordered by distance from the search point. Max 200. Larger values cost more payload and upstream load — prefer tightening filters over raising this."New value: +"Maximum stations to return, ordered by distance from the search point. Max 200."
    • changedOutput schema / properties / stations / items / 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 / stations / items / 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 / stations / items / 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 / stations / items / properties / isRecentlyVerified / description
      Previous value: -"OCM flag: whether the listing was verified recently."New value: +"Whether the listing was verified recently."
  6. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, and the description richly substantiates both: it warns that 'registry status is operator-reported and can be stale' and that 'Open Charge Map is edited continuously, so a station added or removed between pages can shift what a later offset lands on.' It also discloses pagination truncation, mutual-exclusion rejection, and global-by-default behavior beyond what annotations convey.

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?

The description is dense but every sentence earns its place: scope, search modes, geocoding caveat, filter categories, ID resolution, result contents, and pagination. It is front-loaded with the primary purpose and avoids filler or repetition of schema field names.

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 complex 15-parameter tool with an output schema, the description is complete: it covers coordinate prerequisites, filter workflows, result fields, stale-status caveats, and pagination. Since an output schema exists, return-value details do not need to be spelled out, and the description still summarizes them.

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 per-parameter details are already documented (baseline 3). The description adds meaningful cross-parameter guidance: the two mutually exclusive search modes (center+radius vs boundingbox), the integer-ID resolution workflow via openchargemap_lookup_reference, and a coarse 'fast charging only' hint via levelid 3. It stops short of explaining every parameter, but supplements the schema usefully.

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?

Opens with a precise verb+resource+scope: 'Find EV charging stations from the global Open Charge Map registry near a point or within a bounding box.' It also distinguishes itself from siblings by emphasizing coordinate-native search and explicitly stating it 'does not geocode place names', which separates it from lookup/station-detail tools.

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?

Provides explicit routing: geocode places with openstreetmap_geocode first, resolve filter IDs with openchargemap_lookup_reference (including the 'CCS' -> 33 example), and use pagination with nextOffset when a page is truncated. It also states when not to use it in a certain way (don't pass place names; don't mix boundingbox with latitude/longitude as it is rejected).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.