Skip to main content
Glama

get_search_options

Read-onlyIdempotent

List what search_stays accepts: the regions (north, south, center and their sub-regions), the cities that have at least one public listing, the categories and the amenities, each with its slug and a localized name; the search limits (max_nights, max_adults, max_children, max_infants); today in Israel; the accepted payment methods and customer clubs (clubs: ILS checkouts only); the currencies and locales. Call it once before searching when you need a valid region_slug, city_slug, category or amenities slug, and call it when the guest asks whether their club card gets a discount. Facts only, no prices; cached, so a new city or amenity can take up to a day to appear. Read-only.

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": "get_search_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of the region, city, category and amenity names (he, en, fr, es, de, it, ru, ar). Defaults to he.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale / description
      Added value: +"Language of the region, city, category and amenity names (he, en, fr, es, de, it, ru, ar). Defaults to he."
  2. First observed

TDQS

A4/5.0
Behavior3/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 behavior: it returns facts only with no prices, and results are cached so new cities or amenities may lag up to a day. It also notes the clubs restriction to ILS checkouts. Strong additions, but return shape/pagination is only sketched.

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

Conciseness3/5

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

The content inventory is front-loaded and each item earns its place, but it is delivered as one very long clause-chained sentence where the usage instruction (the most actionable part) sits mid-paragraph. Splitting the contents list from the when-to-call guidance would read faster.

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?

There is no output schema, so the description carries the burden of describing the return payload, and it does so thoroughly, down to slugs plus localized names and the max_nights/max_adults limits. The staleness caveat and the ILS-only clubs note close the remaining gaps an agent would need before relying on results.

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?

With a single parameter at 100% schema coverage, the schema already documents locale, its enum and its default of 'he'. The description adds only the indirect hint that names are localized, not which languages or how locale affects the response. Baseline 3 applies.

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?

Opens with a specific verb and object: "List what search_stays accepts", then enumerates the exact contents (regions, cities, categories, amenities, search limits, today in Israel, payment methods, clubs, currencies, locales). This clearly distinguishes it from search_stays, get_stay and get_booking_link, which all consume rather than define the vocabulary.

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

Usage Guidelines5/5

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

Gives an explicit trigger: "Call it once before searching when you need a valid region_slug, city_slug, category or amenities slug", plus a second trigger for club-card discount questions. The word "once" plus the caching note implicitly tells the agent not to re-call per query.

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