Skip to main content
Glama

Live parking occupancy: Karlsruhe region and Leipzig P+R

get_parking_de
Read-only

Free. Free spaces, capacity and occupancy of car parks in the Karlsruhe region (Stadt Karlsruhe open data, CC BY 4.0) and Leipzig Park+Ride facilities (Stadt Leipzig, dl-de/by-2-0), with the reading time of each. A facility that is not real-time, closed or older than live_max_age_min is returned with live=false and no numbers. Source attribution and licence are in every item. Not an official product of the cities; not a guarantee that a space will be free.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name filter, e.g. Leipzig, Rastatt, Karlsruhe
live_onlyNo

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?

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the burden and does add real context: the freshness cutoff (live_max_age_min), the degenerate live=false case with no numbers, per-item source attribution and licence, and an explicit 'not an official product / not a guarantee' disclaimer. It omits operational traits such as rate limits, refresh cadence of the upstream feeds, and what 'Free.' means concretely (no key vs. no cost).

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?

Three sentences, front-loaded with the cost/access signal, then the scope and sources, then the degenerate-case rule and liability disclaimer. The licence identifiers are dense but they are factual attribution that the description itself claims appears in the output, and nothing is repeated from annotations or schema.

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 two optional parameters, no output schema and only safety annotations, the description does the heavy lifting well: it sketches the item payload (numbers plus reading time plus attribution) and the live=false variant. The remaining gap is the undocumented live_only parameter and the unexplained live_max_age_min, which an agent may mistake for an input.

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 50%: 'city' is documented in the schema, while 'live_only' is undocumented there. The description never explains live_only directly, but the live=false rule supplies the underlying concept an agent needs to reason about it. It also references live_max_age_min, which is not a declared parameter, leaving the agent to guess whether that threshold is configurable via this call.

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 names the exact resource (free spaces, capacity and occupancy of car parks), the covered geography (Karlsruhe region and Leipzig Park+Ride) and the upstream data sources, so an agent knows precisely what it returns. It does not differentiate against siblings, but none of the listed siblings overlaps this domain, so the practical ambiguity is low.

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: an agent can infer this is the tool for parking occupancy in those two regions. There is no explicit when-to-use/when-not-to-use statement and no alternative named for other cities or other occupancy datasets. The one behavioral rule given (non-real-time, closed or stale facilities come back with live=false) indirectly tells the agent how to interpret weak results, but not when to choose another tool.

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.