Skip to main content
Glama

Elron Club Public Rentals

Read your viewing arrangements

viewings.get_details
Read-onlyIdempotent

Read session-owned proposals, availability windows, appointments, and post-viewing feedback versions. Includes only customer-facing information and viewing instructions currently released to this customer by the canonical owner; internal notes and unreleased or revoked contact details are excluded.

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>"
    },
    "name": "viewings.get_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionTokenYes

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

B3.3/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds meaningful context by disclosing that internal notes and unreleased or revoked contact details are excluded, which helps the agent understand the visibility boundary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the returned resource types before detailing exclusions. It contains no obvious filler, though the second sentence is dense.

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?

An output schema exists, annotations cover safety traits, and the description explains the content scope and filtering boundaries. The main remaining gap is the lack of any explanation of the sessionToken parameter, but otherwise the definition is sufficient for invocation.

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?

The schema has zero description coverage for the single required sessionToken parameter, and the description does not explain the token's role, format, or constraints beyond the phrase 'session-owned'. It therefore does not compensate for the schema gap.

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 uses a specific verb, 'Read', and names the resource types returned: proposals, availability windows, appointments, and feedback versions. It clearly scopes the data to the customer's session, though it does not explicitly distinguish itself from sibling tools such as 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 Guidelines2/5

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

The description explains what data is returned but gives no explicit guidance on when to use this tool versus alternatives like viewings.get_status or viewings.get_details. Usage is only implied by the content list.

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