Luxembourg MCP

get_cfl_parking

Retrieve live occupancy and details for CFL Park and Ride facilities, helping you find available parking in Luxembourg.

Instructions

Get live occupancy and details for a CFL Park and Ride facility.

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": {
      "parking_id": "<parking_id>"
    },
    "name": "get_cfl_parking"
  }
}

Input Schema

Name	Required	Description	Default
`parking_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and the description only states the action without disclosing behaviors like data freshness, error handling, or required permissions. The agent is left guessing about side effects or limitations.

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 description is a single concise sentence but lacks structure. It front-loads the purpose but omits necessary details, making brevity a drawback rather than an asset.

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

Completeness2/5

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

With a simple tool having one parameter and no output schema, the description should be complete. However, it fails to specify what 'details' are returned or any constraints, leaving the agent underinformed.

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

Parameters1/5

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

The input schema has one required parameter 'parking_id' with no description. The tool description does not explain what a parking_id is or how to obtain it, leaving the agent with no guidance despite 0% schema coverage.

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 description clearly states the verb 'Get' and the resource 'live occupancy and details for a CFL Park and Ride facility.' It distinguishes from sibling tool 'list_cfl_parking' which presumably returns a list of facilities.

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: use to get live data for a specific facility. However, no explicit guidance on when to use versus alternatives like 'list_cfl_parking' or how to obtain the parking_id.

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