Skip to main content
Glama
Sign In

Elron Club Public Rentals

by club.elron
OverviewDiscussionsAdmin

Read public elron club information

information.get
Read-onlyIdempotent

Read the current English or German company, corporate-housing, contact or legal information. Legal documents are information, not acceptance of terms. Personal tenancy facts require the resident portal.

Input Schema

NameRequiredDescriptionDefault
topicYes
localeNode

Output Schema

NameRequiredDescriptionDefault
ucpNo
errorNo
resultNo
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
+]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful semantic context beyond them: legal documents are information rather than acceptance of terms, and personal facts are out of scope. There is no contradiction with the annotations.

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 short sentences, front-loaded with purpose; each sentence adds a distinct scope or boundary clarification. No sentence is redundant or wasted.

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?

For a simple read-only tool with rich annotations and an output schema, the description is largely complete for selection: it covers scope, language and a key exclusion. It leaves individual topic mapping and help-tool alternatives implicit, so it is not fully complete.

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 must carry parameter meaning. It explains locale as English/German and groups topics into company, corporate-housing, contact and legal, but it does not account for all seven enum values (e.g., home, about) or mention the default locale.

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 a specific verb and resource: 'Read the current English or German company, corporate-housing, contact or legal information.' It covers most topic categories, though it does not mention 'home' or 'about' or distinguish this from help.get/help.search.

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?

It states the public-information scope and explicitly redirects personal tenancy facts to the resident portal, which is a useful exclusion. It does not name a sibling tool alternative for general help, so it falls short of full when/when-not/alternatives guidance.

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 toolsInspect
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