Skip to main content
Glama

Openchargemap

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Find Stations

find_stations
Read-onlyIdempotent

Find EV charging stations (electric vehicle chargers) near a place. Pass a location name (city/place, e.g. "San Francisco", "Berlin", "Austin TX") and it is geocoded automatically — OR pass explicit latitude+longitude. Returns nearby charging stations with operator, status, available connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), and distance. Filter by connector type to find e.g. only CCS or Tesla chargers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyNoOptional — your own Open Charge Map API key for higher limits; works without one.
countryNoOptional ISO country code (e.g. "US", "FR") to disambiguate an ambiguous `location` like "Paris" or "Springfield".
distanceNoSearch radius around the location (default 10).
latitudeNoLatitude of the search center, e.g. 37.7749. Optional if `location` is given.
locationNoPlace/city name to search near, e.g. "San Francisco", "Berlin", "Austin TX". Geocoded automatically. Provide THIS or latitude+longitude.
longitudeNoLongitude of the search center, e.g. -122.4194. Optional if `location` is given.
max_resultsNoMaximum number of stations to return (default 20, max 100).
distance_unitNoUnit for the search radius (default "KM").
connection_typeNoOptional connector type name to filter by, e.g. "CCS", "CHAdeMO", "Tesla". Case-insensitive substring match against each station's connector titles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "location": "San Francisco",
+    "max_results": 10
+  },
+  {
+    "connection_type": "CCS",
+    "location": "Berlin"
+  },
+  {
+    "distance": 5,
+    "distance_unit": "KM",
+    "latitude": 37.7749,
+    "longitude": -122.4194
+  }
+]
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Optional ISO country code (e.g. \"US\", \"FR\") to disambiguate an ambiguous `location` like \"Paris\" or \"Springfield\".",
+  "type": "string"
+}
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude of the search center, e.g. 37.7749."New value: +"Latitude of the search center, e.g. 37.7749. Optional if `location` is given."
    • addedInput schema / properties / location
      Added value: +{
+  "description": "Place/city name to search near, e.g. \"San Francisco\", \"Berlin\", \"Austin TX\". Geocoded automatically. Provide THIS or latitude+longitude.",
+  "type": "string"
+}
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude of the search center, e.g. -122.4194."New value: +"Longitude of the search center, e.g. -122.4194. Optional if `location` is given."
    • removedInput schema / required
      Removed value: -[
-  "latitude",
-  "longitude"
-]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds value beyond annotations by describing automatic geocoding, return fields (operator, status, connector types, speed, distance), and filtering capability. Annotations already cover safety; description enhances behavioral understanding.

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?

Four sentences, front-loaded with purpose, then input method, then output, then filter. No redundant information; every sentence earns its place.

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?

Covers main aspects: purpose, input options, returned data, filtering. Lacks mention of defaults (radius, max_results) and pagination, but schema covers those. Adequate for a tool with 9 params and no output schema.

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 baseline is 3. Description adds some clarity (e.g., location input modes) but mostly reiterates schema content without significant extra detail.

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?

Clearly states 'Find EV charging stations near a place' using a specific verb and resource. Distinguishes from sibling 'get_station' which is for a single station.

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?

Explicitly describes when to use: to find stations near a location, with options for location name or lat/lng, and optional filtering. Does not explicitly mention alternatives but effectively communicates its primary use case.

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

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources