Elron Club Public Rentals

Remove your draft request document

applications.remove_document

DestructiveIdempotent

Remove one explicitly selected document from an editable, email-verified request draft, using documentId from applications.list_documents and the current version. Submitted requests remain locked; exact retries replay the receipt.

Input Schema

Name	Required	Description	Default
`confirmed`	Yes
`documentId`	Yes
`sessionToken`	Yes
`idempotencyKey`	Yes
`expectedVersion`	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.2/5.0

Behavior4/5

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

The annotations already declare the operation destructive and idempotent, but the description adds useful state constraints: submitted requests are locked, and exact retries replay the receipt rather than repeating side effects. It does not explicitly mention the confirmed=true requirement, which is an important behavioral precondition for a destructive action.

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 tightly written sentences front-load the core action and scope, then add the critical locked-state and idempotency rules. There is no redundant restatement of the tool name or title.

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?

For a destructive 5-parameter mutation with an output schema, the description covers the key draft-state and retry behavior well. However, with zero schema parameter descriptions, it leaves important invocation details unexplained, especially the mandatory confirmed boolean and sessionToken.

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 documentId (from applications.list_documents) and expectedVersion ('current version'), and hints at retry/idempotency behavior, but it does not explain sessionToken or the required confirmed parameter.

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?

The description gives a precise verb and resource ('Remove one explicitly selected document') and scopes it to an editable, email-verified request draft. It clearly distinguishes this operation from listing documents by naming applications.list_documents as the source of documentId.

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?

It states exactly when removal is allowed (editable, email-verified draft) and when it is not (submitted requests remain locked). It also points to applications.list_documents for obtaining the documentId, leaving little ambiguity about when to use this tool.

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?