Skip to main content
Glama

openchargemap-mcp-server

by io.github.cyanheads

Server Details

Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
cyanheads/openchargemap-mcp-server
GitHub Stars
1
Server Listing
@cyanheads/openchargemap-mcp-server

Available Tools

4 tools
openchargemap_find_stationsopenchargemap-mcp-server: find stationsA
Read-only
Inspect

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.

ParametersJSON 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

ParametersJSON Schema
NameRequiredDescription
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.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, but the description adds substantial behavioral context: the registry is continuously edited so pagination offsets may shift, operational status is operator-reported and can be stale (recommending combination with dateLastVerified and comments), and boundingbox is mutually exclusive with latitude/longitude (rejected, not resolved). It also discloses the 500-station maximum. These details go well beyond the annotations and prepare the agent for real-world variability.

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 longer than typical but every sentence earns its place: it front-loads the core action, then covers coordinate requirement, filter types, ID resolution, result fields, and pagination in a logical order. It avoids repetition and fluff, though it could be slightly trimmed without losing value. Still, it is well-structured and readable.

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 15-parameter tool with multiple search modes, filtering, and pagination, the description is exhaustive: it explains both search patterns, emphasizes the coordinate-native limitation, details the filter ID resolution, describes result contents, and covers pagination with offset behavior and staleness caveats. The presence of an output schema covers return structure, so nothing essential is missing for correct invocation.

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%, so every parameter already has detailed semantics (e.g., distance max 500, levelid meaning, minpowerkw thresholds). The tool description only lists filter categories without adding new parameter-specific guidance beyond what the schema provides. It meets the baseline for a fully documented schema but does not elevate it; no extra insight like practical usage patterns beyond the schema's own examples.

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 opens with a specific verb ('Find') and resource ('EV charging stations from the global Open Charge Map registry'), then immediately scopes the search modes (point/radius or bounding box) and optional country filter. It clearly distinguishes itself from sibling tools by being the station finder, while get_station fetches a single station, get_station_comments fetches comments, and lookup_reference resolves IDs. No ambiguity about what this tool does.

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 states when to use this tool and what to do beforehand: it does not geocode place names, so it instructs to resolve coordinates with openstreetmap_geocode first. It also directs users to resolve filter IDs via openchargemap_lookup_reference, and explains pagination (repeat with nextOffset for truncated results). This gives clear decision criteria and alternative usage, far beyond a generic 'use this for stations' statement.

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

openchargemap_get_stationopenchargemap-mcp-server: get stationA
Read-onlyIdempotent
Inspect

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.

ParametersJSON 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

ParametersJSON Schema
NameRequiredDescription
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.

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.

openchargemap_get_station_commentsopenchargemap-mcp-server: get station commentsA
Read-onlyIdempotent
Inspect

Read community check-ins and comments for one Open Charge Map station — the real-world reliability signal beyond the operator-reported registry status. Returns user comments and fault reports with ratings, dates, and the outcome the driver recorded ("Charged Successfully", "Failed to Charge (Equipment Not Operational)", …), alongside the station's current registry status and last-verified date, surfacing mismatches like "listed operational, but the last few check-ins report a fault." A busy station's check-ins come back one page at a time: when a page reports truncated, repeat the call with the reported nextOffset to read the next one.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesNumeric OCM station ID.
offsetNoComments to skip before the returned page, for reading past a truncated result. Repeat the same call with the nextOffset value the previous one reported. Ordering is newest-first and stable, but a check-in posted between pages shifts what a later offset lands on.
maxresultsNoMaximum comments to return, newest first. Max 100.

Output Schema

ParametersJSON Schema
NameRequiredDescription
capNoThe maxresults cap that was applied.
errorNoPresent when the call failed. Absent on success.
shownNoComments in the returned page.
noticeNoHow to reach the comments this page left out, or why the station has none on record.
commentsNoThe requested page of community comments, newest first — offset/maxresults applied. Empty with totalComments 0 means OCM has no check-ins for this station (absence of reports is not evidence the charger works); empty with a non-zero totalComments means the offset is past the last comment.
stationIdNoOCM station ID the comments belong to.
truncatedNoTrue when comments were left out of the returned page.
nextOffsetNoThe offset to pass on an otherwise identical call to read the next page. Absent on the last page.
totalCountNoComments this station has on record, before the offset/maxresults page was taken — the complete count, not the page size.
attributionNoRequired CC BY 4.0 attribution to Open Charge Map contributors.
stationTitleNoStation name, for context.
isOperationalNoWhether the registry marks the station operational. Absent when the operational state is unknown. Compare against the comments below — they are the real-world check.
totalCommentsNoComments this station has on record — the whole set, before offset/maxresults selected the page in comments. reliabilityNote counts its fault ratio over this population, not over the page.
registryStatusNoCurrent registry operational status (operator-reported).
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.
dateLastVerifiedNoISO 8601 date the listing was last verified. null when never verified.
registryStatusIdNoRegistry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and openWorld hints, so the safety profile is known. The description adds valuable behavioral context beyond that: it states the response contains user comments and fault reports with specific outcome values, alongside registry status and last-verified date, and explains pagination semantics ('a page reports truncated', 'repeat with nextOffset') and ordering ('newest-first'). No contradiction with annotations.

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 three sentences, with the core purpose front-loaded in the first sentence. The second sentence summarizes the output content without unnecessary elaboration, and the third covers pagination concisely. There is no fluff or repetition; every clause 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?

Given the tool's moderate complexity (3 params, one required), existing output schema, and annotations covering safety, the description provides everything needed to call it correctly: purpose, output content, pagination handling, and ordering. The output schema will document return values, so nothing critical is missing.

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% for all three parameters, so the schema already fully documents `id`, `offset`, and `maxresults` including defaults and maximums. The description does not add new parameter-level details beyond what the schema provides; it reinforces the offset pagination behavior but does not extend beyond it. Per the rubric, a baseline of 3 is appropriate.

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 uses a specific verb ('Read') and a clear resource ('community check-ins and comments for one Open Charge Map station'), and immediately differentiates itself from siblings by framing it as 'the real-world reliability signal beyond the operator-reported registry status.' An agent can unmistakably identify this as the tool for retrieving user comments for a specific station, distinct from find_stations (search), get_station (registry details), and lookup_reference (reference data).

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 provides clear context on when to use the tool ('beyond the operator-reported registry status') and gives concrete usage for pagination ('when a page reports truncated, repeat the call with the reported nextOffset'). It does not explicitly name alternative tools or specify when not to use it, but the purpose framing effectively guides selection. The pagination guidance is a strong practical instruction.

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

openchargemap_lookup_referenceopenchargemap-mcp-server: lookup referenceA
Read-onlyIdempotent
Inspect

Resolve Open Charge Map reference data to the integer IDs that openchargemap_find_stations filters require. Pick a category and pass a name or code to resolve — "CCS" or "Tesla Supercharger" -> a connectiontypeid, "ChargePoint" -> an operatorid, "Public - Pay At Location" -> a usagetypeid, "France" or "FR" -> a country. Omit the query to browse the whole category. Large categories come back one page at a time: when a page reports truncated, repeat the call with the reported nextOffset to read the next one.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum entries to return when browsing or when a query matches several. Max 100.
queryNoName, title, code, or alias to resolve (e.g. "CCS", "CHAdeMO", "Tesla", "Public", "France", "FR"). Case-insensitive, matches on title, formal name, and known aliases. Omit to browse the entire category.
offsetNoEntries to skip before the returned page, for reading past a truncated result. Repeat the same call with the nextOffset value the previous one reported. Applies to browsing and to a query with many matches alike; the order is stable, so every entry is reachable by paging.
categoryYesWhich reference set to query. connectiontypes -> connectiontypeid; operators -> operatorid; usagetypes -> usagetypeid; statustypes -> statustypeid; currenttypes -> current type; levels -> charge level (1/2/3); countries -> ISO country.

Output Schema

ParametersJSON Schema
NameRequiredDescription
capNoThe limit that was applied.
errorNoPresent when the call failed. Absent on success.
shownNoEntries in the returned page.
noticeNoHow to reach the entries this page left out.
sourceNoWhere these entries came from. "live" — a startup refresh from Open Charge Map returned a complete set and is what is being served. "bundled" — the snapshot shipped with the server is being served, either because the refresh is switched off or because it failed and the server fell back to the bundle.
matchesNoMatching reference entries, best/exact match first.
categoryNoThe reference category queried.
truncatedNoTrue when matching entries were left out of the returned page.
nextOffsetNoThe offset to pass on an otherwise identical call to read the next page. Absent on the last page.
totalCountNoEntries matching before the offset/limit page was taken — the whole category when browsing, every match when a query was given.
attributionNoRequired CC BY 4.0 attribution to Open Charge Map contributors.
filterParamNoThe find_stations input parameter these IDs feed (e.g. "connectiontypeid"). Omitted for categories with no direct filter (currenttypes; countries use countrycode).
snapshotDateNoDate the reference data in this response was captured, so callers know its vintage — the day the live refresh ran when source is "live", the bundled snapshot's own capture date when source is "bundled". Read it together with source: the same date can mean either a fresh fetch or a freshly cut bundle.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds substantial behavioral detail beyond that: it explains the query matching is case-insensitive and matches aliases, describes pagination behavior ('Large categories come back one page at a time'), and instructs the agent to follow nextOffset for subsequent pages. It also clarifies that offset skips entries and the order is stable. These are valuable runtime behaviors not inferable from annotations alone.

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 a single, dense paragraph with no filler. Every sentence serves a purpose: purpose statement, category-to-ID mapping examples, browsing instruction, and pagination handling. The most important information (what it resolves and for whom) is front-loaded. It is appropriately concise for the tool's complexity.

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?

The tool has an output schema (so return format is externally defined), annotations cover safety and idempotency, and the description explains all operational nuances: category semantics, query behavior, pagination, and offset usage. There is nothing missing that an agent would need to correctly invoke this tool, even for large reference sets. The combination of schema, annotations, and description is complete.

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 schema already provides 100% coverage with descriptive parameter descriptions (e.g., category enum values mapped to ID types, query pattern and alias matching). The description enhances this by giving concrete examples ('CCS' -> connectiontypeid, 'ChargePoint' -> operatorid) and explaining the relationship between offset and nextOffset for paging. This goes beyond the schema's baseline, but since the schema is already thorough, the added value is an incremental improvement rather than a necessity.

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 opens with a specific verb and resource: 'Resolve Open Charge Map reference data to the integer IDs that openchargemap_find_stations filters require.' It names the consumer tool and explicitly differentiates itself from siblings (find_stations is the target, get_station and get_station_comments are unrelated). The mapping examples further clarify the exact role.

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 gives clear, actionable usage context: pick a category, pass a name/code to get an ID, or omit the query to browse. It also explains pagination for large categories. However, it does not explicitly state when not to use this tool versus alternatives (e.g., 'use this only for reference lookups, not station details'), though the purpose statement makes that inference straightforward. Is it explicit enough for a 5? It names the dependent tool, so it effectively guides selection, but the lack of an explicit exclusion directive keeps it at 4.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updates
    • Changedopenchargemap_find_stations6 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"
-]
    • Changedopenchargemap_get_station6 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"
-]
    • Changedopenchargemap_get_station_comments6 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": [
+      "stationId",
+      "stationTitle",
+      "comments",
+      "totalComments",
+      "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: `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: -[
-  "stationId",
-  "stationTitle",
-  "comments",
-  "totalComments",
-  "attribution",
-  "totalCount"
-]
    • Changedopenchargemap_lookup_reference6 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": [
+      "category",
+      "matches",
+      "snapshotDate",
+      "source",
+      "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: `no_match`: No reference entry in the category matched the query. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "no_match"
+          ],
+          "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: -[
-  "category",
-  "matches",
-  "snapshotDate",
-  "source",
-  "attribution",
-  "totalCount"
-]
  2. 4 tool updates
    • Changedopenchargemap_find_stations7 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."
    • Changedopenchargemap_get_station1 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."
    • Changedopenchargemap_get_station_comments9 fields changed
      • addedInput schema / properties / offset
        Added value: +{
+  "default": 0,
+  "description": "Comments to skip before the returned page, for reading past a truncated result. Repeat the same call with the nextOffset value the previous one reported. Ordering is newest-first and stable, but a check-in posted between pages shifts what a later offset lands on.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
      • changedOutput schema / properties / comments / description
        Previous value: -"Community comments, newest first. Empty array means OCM has no check-ins for this station — absence of reports is not evidence the charger works."New value: +"The requested page of community comments, newest first — offset/maxresults applied. Empty with totalComments 0 means OCM has no check-ins for this station (absence of reports is not evidence the charger works); empty with a non-zero totalComments means the offset is past the last comment."
      • addedOutput schema / properties / nextOffset
        Added value: +{
+  "description": "The offset to pass on an otherwise identical call to read the next page. Absent on the last page.",
+  "type": "number"
+}
      • changedOutput schema / properties / notice / description
        Previous value: -"Guidance when the station has no check-ins on record."New value: +"How to reach the comments this page left out, or why the station has none on record."
      • changedOutput schema / properties / shown / description
        Previous value: -"Number of comments returned when the cap was hit."New value: +"Comments in the returned page."
      • addedOutput schema / properties / totalComments
        Added value: +{
+  "description": "Comments this station has on record — the whole set, before offset/maxresults selected the page in comments. reliabilityNote counts its fault ratio over this population, not over the page.",
+  "type": "number"
+}
      • changedOutput schema / properties / totalCount / description
        Previous value: -"Number of comments returned."New value: +"Comments this station has on record, before the offset/maxresults page was taken — the complete count, not the page size."
      • changedOutput schema / properties / truncated / description
        Previous value: -"True when comments were capped at maxresults."New value: +"True when comments were left out of the returned page."
      • changedOutput schema / required
        Previous value: -[
-  "stationId",
-  "stationTitle",
-  "comments",
-  "attribution",
-  "totalCount"
-]New value: +[
+  "stationId",
+  "stationTitle",
+  "comments",
+  "totalComments",
+  "attribution",
+  "totalCount"
+]
    • Changedopenchargemap_lookup_reference9 fields changed
      • addedInput schema / properties / offset
        Added value: +{
+  "default": 0,
+  "description": "Entries to skip before the returned page, for reading past a truncated result. Repeat the same call with the nextOffset value the previous one reported. Applies to browsing and to a query with many matches alike; the order is stable, so every entry is reachable by paging.",
+  "maximum": 9007199254740991,
+  "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 on the last page.",
+  "type": "number"
+}
      • changedOutput schema / properties / notice / description
        Previous value: -"How to reach the entries beyond the cap when a browse was capped."New value: +"How to reach the entries this page left out."
      • changedOutput schema / properties / shown / description
        Previous value: -"Number of entries returned when the cap was hit."New value: +"Entries in the returned page."
      • changedOutput schema / properties / snapshotDate / description
        Previous value: -"Date the bundled reference snapshot was captured, so callers know the data vintage."New value: +"Date the reference data in this response was captured, so callers know its vintage — the day the live refresh ran when source is \"live\", the bundled snapshot's own capture date when source is \"bundled\". Read it together with source: the same date can mean either a fresh fetch or a freshly cut bundle."
      • addedOutput schema / properties / source
        Added value: +{
+  "description": "Where these entries came from. \"live\" — a startup refresh from Open Charge Map returned a complete set and is what is being served. \"bundled\" — the snapshot shipped with the server is being served, either because the refresh is switched off or because it failed and the server fell back to the bundle.",
+  "enum": [
+    "live",
+    "bundled"
+  ],
+  "type": "string"
+}
      • changedOutput schema / properties / totalCount / description
        Previous value: -"Number of entries returned."New value: +"Entries matching before the offset/limit page was taken — the whole category when browsing, every match when a query was given."
      • changedOutput schema / properties / truncated / description
        Previous value: -"True when a browse was capped at limit."New value: +"True when matching entries were left out of the returned page."
      • changedOutput schema / required
        Previous value: -[
-  "category",
-  "matches",
-  "snapshotDate",
-  "attribution",
-  "totalCount"
-]New value: +[
+  "category",
+  "matches",
+  "snapshotDate",
+  "source",
+  "attribution",
+  "totalCount"
+]
  3. 4 tool updates
    • Changedopenchargemap_find_stations6 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"
+}
    • Changedopenchargemap_get_station5 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"
+}
    • Changedopenchargemap_get_station_comments5 fields changed
      • addedOutput schema / 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 / 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 / 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 / comments / items / properties / relatedUrl
        Added value: +{
+  "description": "Link the commenter attached. Absent when none was given.",
+  "type": "string"
+}
      • addedOutput schema / properties / registryStatusId
        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"
+}
    • Changedopenchargemap_lookup_reference3 fields changed
      • removedInput schema / properties / query / minLength
        Removed value: -1
      • addedInput schema / properties / query / pattern
        Added value: +"\\S"
      • changedOutput schema / properties / notice / description
        Previous value: -"Guidance when a query matched nothing."New value: +"How to reach the entries beyond the cap when a browse was capped."
  4. 4 tool updates
    • Changedopenchargemap_find_stations5 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."
    • Changedopenchargemap_get_station6 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."
    • Changedopenchargemap_get_station_comments4 fields changed
      • changedInput schema / properties / id / description
        Previous value: -"Numeric OCM station ID. Get one from openchargemap_find_stations. Note: UUID lookup is not supported by the OCM API."New value: +"Numeric OCM station ID."
      • changedInput schema / properties / maxresults / description
        Previous value: -"Maximum comments to return (handler trims, newest first). The OCM API returns all embedded comments — this caps what the tool surfaces. Max 100."New value: +"Maximum comments to return, newest first. Max 100."
      • changedOutput schema / properties / isOperational / description
        Previous value: -"Whether the registry marks the station operational. Absent (not null) when status is Unknown — OCM omits the flag then. Compare against the comments below — they are the real-world check."New value: +"Whether the registry marks the station operational. Absent when the operational state is unknown. Compare against the comments below — they are the real-world check."
      • changedOutput schema / properties / reliabilityNote / description
        Previous value: -"Server-computed caveat when status and comments disagree or the listing is stale (plain prose from observable facts; no synthetic score). Omitted when nothing to flag."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."
    • Changedopenchargemap_lookup_reference2 fields changed
      • changedOutput schema / properties / matches / description
        Previous value: -"Matching reference entries, best/exact match first. Use the id in a find_stations filter."New value: +"Matching reference entries, best/exact match first."
      • changedOutput schema / properties / matches / items / properties / id / description
        Previous value: -"The reference ID — pass to the matching openchargemap_find_stations filter (e.g. connectiontypeid)."New value: +"The reference ID for this entry."
  5. 4 tool updates
    • First observedopenchargemap_find_stations
    • First observedopenchargemap_get_station
    • First observedopenchargemap_get_station_comments
    • First observedopenchargemap_lookup_reference

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

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