Elron Club Public Rentals

Check verified rental availability

rentals.check_availability

Read-onlyIdempotent

Check the current published availability state and earliest date for one rental. This does not create a hold or reservation.

Input Schema

Name	Required	Description	Default
`locale`	No		de
`rentalId`	Yes

Output Schema

Name	Required	Description	Default
`ucp`	No
`error`	No
`result`	No
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 31, 2026

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "retryable": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "code",
+    "message",
+    "retryable"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / status / const
```
Removed value: -"completed"
```

addedOutput schema / properties / status / enum

Added value: +[
+  "completed",
+  "error"
+]

addedOutput schema / properties / ucp

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "capabilities": {
+      "additionalProperties": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "version": {
+              "const": "2026-07-13",
+              "type": "string"
+            }
+          },
+          "required": [
+            "version"
+          ],
+          "type": "object"
+        },
+        "maxItems": 1,
+        "minItems": 1,
+        "type": "array"
+      },
+      "propertyNames": {
+        "enum": [
+          "club.elron.rentals.discovery",
+          "club.elron.rentals.application",
+          "club.elron.rentals.viewing",
+          "club.elron.rentals.quote",
+          "club.elron.rentals.booking",
+          "club.elron.rentals.waitlist"
+        ],
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "version": {
+      "const": "2026-04-08",
+      "type": "string"
+    }
+  },
+  "required": [
+    "version",
+    "capabilities"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "status",
-  "result"
-]New value: +[
+  "status"
+]

Changed6 schema fields changedJul 14, 2026

changedOutput schema / properties / result / properties / availability / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / result / properties / availability / properties / availableFrom

Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / result / properties / availability / properties / canStartInquiry
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / result / properties / availability / properties / status

Added value: +{
+  "enum": [
+    "AVAILABLE",
+    "UPCOMING",
+    "UNAVAILABLE"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / result / properties / availability / properties / verifiedAt

Added value: +{
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+  "type": "string"
+}

addedOutput schema / properties / result / properties / availability / required

Added value: +[
+  "status",
+  "availableFrom",
+  "verifiedAt",
+  "canStartInquiry"
+]

First observedJul 14, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the description doesn't need to prove safety. What it adds is the 'published' qualifier (a point-in-time public state, not internal inventory) and the explicit no-hold guarantee, but nothing on staleness, timezone, or rate limits. Useful reinforcement rather than new behavioral depth.

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?

Two short sentences, both earning their place: the first states what is returned, the second removes the most likely misreading. Front-loaded with zero preamble.

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 an output schema present, the description needn't explain return values, and it covers scope, single-rental targeting, and the no-hold caveat. Minor gaps remain around whether 'availability' accounts for partial periods or locale-dependent output, but nothing essential for a correct call is missing.

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 0%, so the description has to carry parameter meaning. 'for one rental' correctly conveys that rentalId targets a single record, but the locale parameter (enum de/en, default de) is never mentioned or explained. Partial compensation is the right level here.

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?

Names a specific verb ('check') and a precisely scoped resource: the current published availability state and earliest date for a single rental. This clearly separates it from rentals.get (full record), rentals.get_pricing, and viewings.propose_availability, which an agent can distinguish 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'This does not create a hold or reservation' is a genuine exclusion that steers an agent away from treating the result as a booking step. No alternative tool is named for the case where the caller actually wants to hold dates, so it stops short of full when/when-not routing.

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

All Elron Club Public Rentals tools Inspect

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

Need Help?