Skip to main content
Glama

Ladeeinrichtungen suchen

search_charging_stations
Read-onlyIdempotent

Sucht Ladeeinrichtungen im Ladesäulenregister der Bundesnetzagentur (Stand 12.11.2026). Mindestens ein Ortsfilter (plz, ort, kreis, bundesland) oder betreiber ist nötig. Liefert die Gesamtzahl der Treffer und bis zu 'limit' Einrichtungen (id, betreiber, adresse, plz, ort, kreis, bundesland, lat, lon, inbetriebnahme, ladepunkte, ladepunkt_leistungen_kw, summe_kw, max_kw, schnellladepunkte, steckertypen), sortiert nach Summe der Nennleistungen der Ladepunkte. Betreiber ohne erkennbare Rechtsform erscheinen nicht namentlich, Adresse und Koordinaten sind dort vergröbert. Searches charging stations in the German federal charging register (as of 2026-11-12). At least one location filter or 'betreiber' is required. Returns total hit count and up to 'limit' stations, sorted by power.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_charging_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
ortNoOrtsname, z. B. 'Leipzig' / Town or city name
plzNoPostleitzahl oder Präfix, z. B. '04' oder '04109' / Postal code or prefix
kreisNoKreis oder kreisfreie Stadt, z. B. 'Leipzig' oder 'Landkreis Leipzig' / District
limitNoMaximale Zahl Treffer in der Liste (Standard 20, max. 50) / Max results
min_kwNoMindestens ein Ladepunkt der Einrichtung hat diese Nennleistung in kW / At least one charge point has this rated power (kW) or more
betreiberNoTeilstring des Betreibernamens (nur Betreiber mit erkennbarer Rechtsform), z. B. 'EnBW' / Operator name substring (legal entities only)
bundeslandNoBundesland, z. B. 'Sachsen' / Federal state
nur_schnellladenNoNur Einrichtungen mit mindestens einem Schnellladepunkt (Ladepunkt über 22 kW, § 2 LSV) / Only stations with at least one fast charging point (above 22 kW)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive, closed-world), the description discloses the data vintage (Stand 12.11.2026), the sort order (sum of rated charge-point power), that a total hit count is returned alongside a truncated list, and a non-obvious data-quality caveat: operators without a recognizable legal form are not named and their address/coordinates are coarsened.

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?

Wait — revised: the content is stated twice (full German text then a compressed English restatement), which does not add information for an agent that reads either language. Combined with the long inline field enumeration, roughly half the text is structural redundancy rather than new substance.

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?

With no output schema, the description compensates by listing the returned fields and the total-count behavior, and it covers the truncation bound via 'limit'. For a read-only, zero-required-parameter search tool, an agent has everything needed to call it correctly without follow-up questions.

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%, so the baseline is 3; the field-level bilingual descriptions already carry the parameter meanings. The description does add one thing the schema cannot express — the at-least-one-filter constraint, since the schema declares zero required parameters — but otherwise adds little parameter detail (e.g. no note on how min_kw interacts with nur_schnellladen).

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?

The description states a specific verb and resource ("Sucht Ladeeinrichtungen im Ladesäulenregister der Bundesnetzagentur") plus the data snapshot date, which an agent can act on immediately. It does not differentiate itself from the siblings (dataset_info, region_statistics, register_changes), so an agent must infer the boundary on its own.

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?

It gives an explicit precondition — at least one location filter (plz, ort, kreis, bundesland) or betreiber is required — which is real usage guidance. It never says when a different tool (e.g. aggregate statistics or change listings) is the better choice, so there is context but no exclusions or named alternatives.

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