Elron Club Public Rentals

Search the elron club Help Center

help.search

Read-onlyIdempotent

Search approved general DE/EN guidance for applicants, residents and coworking guests. Returns article IDs and canonical links. For emergency guidance and schedule-based office-hours status, call help.get with articleId after-hours-emergencies. Use rentals tools for current apartment availability and prices; personal tenancy details require the resident's own portal.

Input Schema

Name	Required	Default
`limit`	No
`query`	No
`locale`	No	de
`offset`	No
`category`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026

addedOutput schema / properties / result / properties / items / 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 / items / items / properties / broaderArticleId
```
Added value: +{
+  "type": "string"
+}
```

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

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

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds meaningful scope boundaries: the corpus is 'approved' (curated) content only, it excludes personal tenancy data and live pricing, and results are IDs plus canonical links. It does not describe pagination behavior or how locale affects results, which keeps it below the top score.

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, zero filler: purpose first, return shape second, routing/exclusions last. Every clause carries distinct information and the most decision-relevant content is front-loaded.

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?

Annotations and the output schema cover safety and return values, and sibling routing is complete, but with 0% schema description coverage the definition leaves the agent without guidance on category selection or paging (limit 1-30, offset to 1000). Adequate overall, yet not fully self-sufficient for invocation.

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% across five parameters, so the description must compensate and mostly doesn't: only the DE/EN axis is implied via 'DE/EN guidance'. The query, category enum values, limit range and offset/paging semantics are never explained in prose, leaving the agent to read raw schema types alone.

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 concrete verb+resource ('Search ... Help Center guidance') and pins the content domain and audiences ('approved general DE/EN guidance for applicants, residents and coworking guests'). It also names the return shape (article IDs and canonical links), which separates it cleanly from sibling help.get.

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

Usage Guidelines5/5

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

Explicitly routes three adjacent needs elsewhere: emergency guidance and office-hours status go to help.get with articleId after-hours-emergencies, apartment availability/prices go to rentals tools, and personal tenancy details require the resident's portal. Both when-to-use and when-not-to-use are stated with named alternatives.

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?