Elron Club Public Rentals

Read an elron club help article

help.get

Read-onlyIdempotent

Read the same approved localized article as the public website, including related answers and next steps. after-hours-emergencies also returns schedule-based office-hours status in Europe/Zurich, the observation time, the published schedule and Swiss emergency numbers. A message does not guarantee immediate attendance. Historical examples never override an individual signed agreement. Returns no apartment credentials, staff notes or individual case data.

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / result / properties / officeHours

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "closedDates": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "label": {
+      "type": "string"
+    },
+    "observedAt": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "periods": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "closes": {
+            "type": "string"
+          },
+          "opens": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "opens",
+          "closes"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "state": {
+      "enum": [
+        "OPEN",
+        "CLOSED",
+        "UNKNOWN"
+      ],
+      "type": "string"
+    },
+    "timeZone": {
+      "const": "Europe/Zurich",
+      "type": "string"
+    },
+    "weekdays": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "state",
+    "observedAt",
+    "timeZone",
+    "label",
+    "weekdays",
+    "periods",
+    "closedDates"
+  ],
+  "type": "object"
+}

Changed9 schema fields changedOct 24, 2026

addedOutput schema / properties / result / properties / applicability

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "kind": {
+      "enum": [
+        "GLOBAL",
+        "PROPERTY",
+        "UNIT"
+      ],
+      "type": "string"
+    },
+    "labels": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "kind",
+    "labels"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / properties / broaderArticleId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / result / properties / publication

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "publishedAt": {
+      "type": "string"
+    },
+    "version": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "version",
+    "publishedAt"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / properties / relatedArticles / items / properties / applicability

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "kind": {
+      "enum": [
+        "GLOBAL",
+        "PROPERTY",
+        "UNIT"
+      ],
+      "type": "string"
+    },
+    "labels": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "kind",
+    "labels"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / properties / relatedArticles / items / properties / broaderArticleId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / result / properties / relatedArticles / items / properties / publication

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "publishedAt": {
+      "type": "string"
+    },
+    "version": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "version",
+    "publishedAt"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / properties / sections / items / properties / images

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "alt": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "alt"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / result / properties / sections / items / properties / links

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "label",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / result / properties / sections / items / properties / table

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "headers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rows": {
+      "items": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "headers",
+    "rows"
+  ],
+  "type": "object"
+}

AddedOct 23, 2026

TDQS

B3.4/5.0

Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description still adds substantial context: content parity with the public site, a special-case return shape for the after-hours-emergencies article (Europe/Zurich schedule status, observation time, published schedule, Swiss emergency numbers), interpretation caveats, and explicit negative disclosure of what is NOT returned (credentials, staff notes, case data).

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?

Purpose is front-loaded in the first sentence and no sentence is pure filler. The after-hours sentence is very dense and the two policy-style caveats are borderline, but they do inform how an agent should present the returned content rather than being repetition.

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

Completeness3/5

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

An output schema exists and annotations are rich, so return values and safety are adequately covered, and the special-case return is even explained. The remaining gap is parameters: with 0% schema coverage, the agent gets no guidance on what articleId accepts or how locale behaves, which is the one thing needed to call this correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does not. 'Localized' only hints at the locale parameter without naming it or its de/en values, and 'after-hours-emergencies' hints at an articleId value but never documents the articleId format, length limits, or the de default.

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?

States a specific verb and resource ('Read ... article') and adds a meaningful guarantee: the content is the same approved localized article served on the public website, including related answers and next steps. It never names help.search, so the get-vs-search distinction is left implicit, which keeps it out of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to call this versus help.search, and no mention that an articleId must already be known. The only implicit signal is that the tool takes a specific article ('after-hours-emergencies'), which an agent could infer means 'use search first', but the description never says so.

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?