Skip to main content
Glama

Elron Club Public Rentals

Accept or decline a viewing proposal

viewings.respond_to_proposal
Idempotent

Accept or decline one pending Elron Club proposal with explicit confirmation, an exact application version, and a durable idempotency key. Acceptance may send the existing viewing confirmation communication.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "expectedVersion": "<expectedVersion>",
      "action": "<action>",
      "responseConfirmed": "<responseConfirmed>",
      "sessionToken": "<sessionToken>",
      "proposalId": "<proposalId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "viewings.respond_to_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
proposalIdYes
sessionTokenYes
idempotencyKeyYes
expectedVersionYes
responseConfirmedYes

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. Changed1 schema field changed
    • changedOutput schema / properties / result / properties / status / enum
      Previous value: -[
      -  "PROPOSED",
      -  "ACCEPTED",
      -  "DECLINED"
      -]New value: +[
      +  "PROPOSED",
      +  "ACCEPTED",
      +  "DECLINED",
      +  "WITHDRAWN",
      +  "EXPIRED"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations (idempotentHint=true, destructiveHint=false, openWorldHint=true), the description adds important behavioral context: explicit confirmation is required, the application version must match exactly, the idempotency key is durable, and acceptance may send a viewing confirmation communication. It does not describe error behavior for version conflicts, but the added side-effect disclosure is valuable.

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 follow with the most important side-effect caveat. There is no redundant restatement of the title or schema.

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 has an output schema and annotations, so the description need not explain return values or the safety profile. It covers the confirmation, version, idempotency, and communication side effect well, though it leaves sessionToken semantics and version-conflict behavior unaddressed.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries most of the burden. It clarifies action (accept/decline), proposalId (one pending proposal), expectedVersion (exact application version), responseConfirmed (explicit confirmation), and idempotencyKey (durable idempotency key). sessionToken is not explained, but the remaining parameters are meaningfully grounded.

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 states a specific verb pair (accept or decline), the exact resource (one pending Elron Club proposal), and the scope constraint that it applies to a single pending proposal. This is enough to distinguish it from sibling operations such as viewings.propose_availability and viewings.get_status.

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

Usage Guidelines3/5

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

The description implies usage by saying it operates on 'one pending Elron Club proposal' and offers only ACCEPT/DECLINE actions, but it does not explicitly compare against siblings like viewings.get_status or state when not to use this tool. The context is clear but alternatives are left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources