Skip to main content
Glama

Elron Club Public Rentals

Find public apartment locations

locations.search
Read-onlyIdempotent

Find published apartment buildings by city, region or name. Returns public locationId slugs for locations.get; no private property identifiers are returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "locations.search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
localeNode
offsetNo

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: results are limited to published/public locations and private property identifiers are excluded, which tells the agent what will and will not come back.

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: purpose and matching facets first, then the return contract and follow-up tool. Nothing is repeated from the schema or annotations and no sentence is padding.

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 annotations and an output schema already covering safety and payload shape, the description only needs to convey what is searched and what is returned, which it does, including the public-only guarantee. The remaining gap is the lack of any hint about paging or the query string's free-text nature.

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 carries the full burden for four parameters, yet it never names 'query' or explains how city/region/name map onto it (single string? free text?). Limit, offset and locale are not mentioned at all, leaving pagination and language behavior entirely to structural inference.

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?

States a specific verb and resource ('Find published apartment buildings') with the searchable facets (city, region, name) and scopes the result to public data only. It also explicitly separates itself from the sibling locations.get by naming it as the follow-up consumer of the returned locationId slugs.

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 workflow ('returns locationId slugs for locations.get') implies when to call it, but there is no explicit when-not guidance or comparison against adjacent discovery tools such as regions.list or rentals.search. The agent can infer the sequence but must guess the boundaries.

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