Skip to main content
Glama

Find EV charging stations near a point

get_ev_chargers_nearby
Read-only

Find EV charging stations near WGS84 coordinates, with operator, plugs, power, access and distance from Swiss public data, sorted by proximity.

Instructions

EV charging stations from the national ich-tanke-strom.ch dataset near WGS84 coordinates: operator, plugs, max power, 24h access, address and number of charge points (evse_count) per station. Sorted by distance.

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": "get_ev_chargers_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude
lonYesWGS84 longitude
limitNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context (dataset provenance, distance sorting, returned fields) but says nothing about how limit/radius interact, whether results are truncated, or what happens when nothing is found.

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?

A single front-loaded sentence that leads with the resource and dataset, then lists outputs. The attribute list is dense but every element is informative; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates return fields, which is the right call. However, for a 4-parameter geo query it leaves the two optional parameters (limit, radius_km) and result-truncation behavior unexplained, which an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: lat/lon are documented in the schema, but limit and radius_km have no descriptions anywhere. The description mentions coordinates and distance ordering but never explains the radius unit, default, cap, or what limit controls, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('EV charging stations ... near WGS84 coordinates') and names the source dataset (ich-tanke-strom.ch), plus enumerates the returned attributes. It is clearly distinguishable from generic siblings like get_nearby_stations, though it never explicitly contrasts itself with them.

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 only implied: the coordinate-based framing and 'Sorted by distance' tell an agent this is a proximity lookup, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as get_nearby_stations for other POI types.

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

Deploy Server

Other Tools