Elron Club Public Rentals

Open your verified request document

applications.get_document

Read-onlyIdempotent

Return an authenticated binary-download URL for one document owned by the email-verified session. The link contains a scoped credential: do not share or log it. Use documentId from applications.list_documents.

Input Schema

Name	Required	Description	Default
`documentId`	Yes
`sessionToken`	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 changedNov 2, 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"
+]

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds important context beyond annotations: the returned URL contains a scoped credential and should not be shared or logged, and the document must belong to the email-verified session.

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 the core action and followed by the security warning and parameter-source guidance. Every sentence contributes useful information with no repetition or filler.

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?

The tool is a read-only retrieval operation with annotations and an output schema, so return-format details are not required. The description covers the security-sensitive credential behavior and documentId sourcing, though it leaves sessionToken semantics under-explained.

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. It explains where documentId comes from via applications.list_documents, but it does not explain the required sessionToken parameter beyond an implicit reference to the email-verified session.

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 specific verb and resource: return an authenticated binary-download URL for one document. It also scopes the operation to documents owned by the email-verified session, which distinguishes it from list/upload/remove document operations.

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?

Explicitly tells the agent to use documentId from applications.list_documents, which gives a clear call sequence. It does not state when not to use it or name alternatives for other document actions, but the retrieval use case is unambiguous.

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?