Skip to main content
Glama

Search EV Charging Stations

ev.charging.search
Read-onlyIdempotent

Locate EV charging stations globally by location, country, operator, connector, and power. Set a minimum power threshold to identify fast-charging stations.

Instructions

Search 300K+ EV charging stations worldwide by location, country, operator, connector type, and power level. Returns station address, GPS coordinates, connectors (Type 2, CCS, CHAdeMO), power kW, operator, status. Filter by min power for fast charging. Largest open EV charging database (Open Charge Map)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeNoISO 2-letter country code to filter by (e.g. "US", "GB", "DE")
latitudeNoLatitude for location-based search (e.g. 51.5074)
longitudeNoLongitude for location-based search (e.g. -0.1278)
distanceNoSearch radius in distance_unit (default KM)
distance_unitNoDistance unit: KM or Miles (default KM)
operator_idNoFilter by charging network operator ID
connection_type_idNoFilter by connector type (e.g. 25=Type 2, 33=CCS, 2=CHAdeMO)
min_power_kwNoMinimum charger power in kW (e.g. 50 for fast charging)
status_type_idNoFilter by status (50=Operational, 100=Not Operational)
limitNoMaximum results to return (1-100, default 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.5.1
  2. Removed
  3. Addedv1.5.0
  4. Removedv1.0.20
  5. Addedv1.0.17

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds value by enumerating return fields (address, coordinates, connector types, power, operator, status) and explicitly mentions the min_power_kw filter for fast charging, providing behavioral context beyond the 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 two sentences, front-loaded with the main purpose and key filters. It is concise with no redundant information. Every part contributes to understanding the tool's functionality.

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?

Given the tool's 10 optional parameters and the presence of an output schema, the description adequately covers the search functionality, return fields, and key filtering options. It mentions the data source (Open Charge Map) but could explicitly note pagination behavior or limit defaults more clearly.

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% with detailed parameter descriptions. The description adds context by naming specific connector types (Type 2, CCS, CHAdeMO) and mentioning 'min power for fast charging', which elaborates on the min_power_kw parameter. This adds value beyond the 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?

The description clearly states the tool searches 300K+ EV charging stations worldwide with specific filters (location, country, operator, connector type, power level), and names the return fields. It distinguishes from siblings like ev.charging.nearby and ev.charging.details by emphasizing the comprehensive database and multiple filter options.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context through the mention of '300K+' stations, 'Largest open EV charging database', and filter options, implying broad applicability. However, it does not explicitly state when to use this tool versus alternatives like ev.charging.nearby or ev.charging.details.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server