Skip to main content
Glama

Elron Club Public Rentals

Record your decision after a viewing

viewings.respond_after_viewing
Idempotent

Record PROCEED, NOT_INTERESTED, NEEDS_ALTERNATIVES or ANOTHER_VIEWING for one elapsed appointment from viewings.get_details. Requires the current request version, exact feedbackVersion and explicit customer confirmation. Proceeding does not submit a Request or create a booking.

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": {
      "sessionToken": "<sessionToken>",
      "expectedVersion": "<expectedVersion>",
      "idempotencyKey": "<idempotencyKey>",
      "confirmed": "<confirmed>",
      "appointmentId": "<appointmentId>",
      "feedbackVersion": "<feedbackVersion>",
      "response": "<response>"
    },
    "name": "viewings.respond_after_viewing"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
responseYes
confirmedYes
sessionTokenYes
appointmentIdYes
idempotencyKeyYes
expectedVersionYes
feedbackVersionYes

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.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (non-read-only, idempotent, non-destructive, open-world), and the description adds genuinely new behavioral context: that proceeding does not submit a Request or create a booking, which is a key side-effect boundary an agent needs. It does not cover retry/idempotency or error semantics, so not a 5.

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 packed sentences, front-loaded with the decision enumerations and followed by prerequisites and the no-side-effect caveat. Every clause adds information; nothing is 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?

With an output schema present, return values needn't be described, and the description supplies the decision semantics, prerequisites, and the crucial 'no Request/booking' boundary. It leaves session/authentication and idempotency-key semantics unspoken, a modest gap for an 8-parameter mutation.

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 coverage is 0%, so the description must carry the burden, and it partially does: expectedVersion is glossed as 'current request version', feedbackVersion as 'exact feedbackVersion', confirmed as 'explicit customer confirmation', and response maps to the four enum values plus appointmentId ('one elapsed appointment'). However sessionToken, idempotencyKey and note are unaddressed, leaving meaningful gaps.

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?

Specific verb 'Record' plus the four enumerated decision outcomes and a precise scope ('one elapsed appointment from viewings.get_details'). This is clearly distinguishable from siblings like viewings.respond_to_proposal and viewings.proceed_without_viewing.

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?

Names the prerequisite tool (viewings.get_details) and the preconditions (current request version, exact feedbackVersion, explicit customer confirmation), giving clear when-to-use context. It does not explicitly exclude or route away from the near-siblings respond_to_proposal / proceed_without_viewing, so no full 5.

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