Skip to main content
Glama

EV charging stations near a point

auto_plugshare
Read-only

EV charging stations near a point. Primary source OpenStreetMap (Overpass): name, operator, network, socket types, capacity, access, hours. For US points when Overpass is unavailable, the US DOE/NREL Alternative Fuel Stations directory is used instead. PlugShare itself has no public API, so its reviews and live status are not included. Related tools on this server, for a different need: auto_carsdirect_vehicle when you need CarsDirect used-car listings near a US ZIP code: vehicle; auto_autonation when you need AutoNation cars for sale for a make and optional model. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "auto_plugshare"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude -90 to 90
lonYesLongitude -180 to 180
limitNoMax stations, 1 to 50 (default 10)
radiusNoSearch radius in metres, 100 to 10000 (default 2000)

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
stationsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the primary and fallback data sources and a real limitation — PlugShare reviews and live station status are absent because there is no public API. It also states per-call pricing ($0.002, x402/USDC) and that failed calls are not charged, which the annotations cannot convey. It does not cover result ordering or pagination, keeping it short of a 5.

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

Conciseness3/5

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

The purpose and provenance sentences are front-loaded and earn their place, and the pricing note is compact. However, the 'Related tools on this server' block about CarsDirect and AutoNation is irrelevant filler for an EV-charging lookup and occupies a large share of the text, burying the useful caveats.

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?

With an output schema present, the description need not explain return values, and the annotations cover read-only/open-world safety; sourcing, coverage gaps and cost are all stated. The only missing piece is differentiation from the other EV/charging tools in the catalog, which the irrelevant sibling block actively distracts from.

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 coverage is 100%, with lat/lon ranges, radius in metres (100–10000, default 2000) and limit (1–50, default 10) all documented in the schema itself. The description adds nothing about parameter behavior — e.g. whether radius interacts with the fallback source or what happens when the limit truncates results — so the baseline 3 applies.

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 first sentence names a specific resource and scope ('EV charging stations near a point'), and the following sentences enumerate exactly what comes back (name, operator, network, socket types, capacity, access, hours) plus which sources back it. An agent knows this is a geospatial lookup of charging infrastructure, not vehicle listings or catalog search.

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?

Usage is implied by the source-fallback note ('for US points when Overpass is unavailable, the DOE/NREL directory is used'), which is useful context but not a when-to-use rule the agent controls. There is no exclusion or comparison against the genuinely related siblings in the catalog (auto_ev_database, auto_data_wa_gov_electric_vehicle); the 'related tools' block instead names CarsDirect and AutoNation, which serve entirely different needs and offer no routing value.

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.

Resources