Skip to main content
Glama

Elron Club Public Rentals

Get the verified applicant's contract signing link

contracts.get_signing_link
Read-onlyIdempotent

Return a secure signing URL only when the active signer invitation email matches the email-verified application session. Human verification, review, and signature remain in the signing flow.

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": "contracts.get_signing_link"
  }
}

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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: the URL is gated on signer-invitation email matching the verified session, and verification/review/signature are explicitly not performed here. It does not say what is returned when the condition fails, which is the remaining gap.

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 tight sentences with no waste, and the gating condition is front-loaded before the scope disclaimer. Every clause carries information the agent needs.

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, so return-value shape need not be explained, and the description covers the security precondition and the tool's boundary. The one missing piece is behavior on a failed match (error vs. empty result), which an agent calling this would want to know.

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 description coverage is 0%, so the single required 'sessionToken' has no documented meaning in the schema. The description partially compensates by tying it to an 'email-verified application session', but it never states the token's origin, format, or failure mode when expired or mismatched.

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 names a specific verb and resource ('Return a secure signing URL') and scopes it to an email-matched, verified application session. It is unambiguous about what the tool produces, though it never names or contrasts a sibling, which is acceptable given no sibling in the list overlaps with this function.

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 email-match condition is a success precondition rather than a statement of when to call the tool versus something else. An agent can infer this is the step after human verification and review, but no alternative paths or exclusions are stated, so usage is implied rather than guided.

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