Skip to main content
Glama
Sign In

Ladepunktdaten

by de.ladepunktdaten
OverviewDiscussionsAdmin

Registeränderungen 01.09. bis 30.09.2026

register_changes
Read-onlyIdempotent

Änderungen im Ladesäulenregister zwischen den Registerständen 01.09.2026 und 30.09.2026: neu gemeldet, aus dem Register entfernt (Ursache unbekannt, nicht gleich stillgelegt), Felder geändert. Filter wie bei der Suche, alle optional. Zählungen sind immer vollständig; Einzeldatensätze nur als Probe (max. 10, ohne Alt-/Neuwerte, nur Namen der geänderten Felder). Changes in the register between the 2026-09-01 and 2026-09-30 snapshots. Counts are complete; individual records are a sample of at most 10 (field names only, no old/new values).

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

Input Schema

NameRequiredDescriptionDefault
artNoArt der Änderung für die Probe / Kind of change for the samplealle
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
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

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the asymmetrical result shape: counts are always complete but individual records are a sample of at most 10 with fieldnames only and no old/new values. It also clarifies that 'entfernt' has an unknown cause and does not imply decommissioning. What is missing is the shape of the count breakdown and any notion of result ordering.

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?

The German text is front-loaded and efficient, leading with scope then result semantics. The full English restatement is largely redundant duplication that inflates length without adding information.

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?

For a tool with no output schema, the description supplies the essential return-value semantics (complete counts, capped sample, no old/new values), which is what an agent most needs. A description of the count structure per change class would close the remaining gap.

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 the eight parameters are already fully documented with examples and units. The description adds only that all filters are optional and mirror the search tool's filters; it does not explain non-obvious interactions such as how `art` scopes the sample versus the counts.

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?

States a specific verb and resource ('Änderungen im Ladesäulenregister'), the exact comparison window (01.09.2026–30.09.2026), and the three change classes (neu gemeldet / entfernt / Felder geändert). This lets an agent tell it apart from search_charging_stations (current state) without opening the schema.

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?

'Filter wie bei der Suche, alle optional' signals that the same filtering semantics as the search tool apply, which is useful context. However, it never states when to prefer this tool over search_charging_stations or region_statistics, and gives no exclusion conditions; the choice between change-history and current-state queries is left to inference.

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

All Ladepunktdaten 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