Skip to main content
Glama

Livuma — Bali rental & property search

Get search options

get_search_options
Read-onlyIdempotent

Returns the valid listing-search values: property types, ownership types, common areas, currencies, rental modes and amenity names, plus notes on paging, budgets and bookability.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description rightly does not repeat it. What it adds is payload-level context — that paging, budget and bookability notes are included alongside the value lists — which is useful but thin. It says nothing about caching/staleness of the returned values or whether they vary by context, which is the main behavioral question for a static-options endpoint.

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?

One sentence, front-loaded with the outcome ("Returns the valid listing-search values") followed by the enumerated contents. No filler, no restatement of the title, and the enumeration is the highest-value content for an agent deciding whether to call it.

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 value, and it does so by naming each category plus the accompanying notes. The gap is granularity: it doesn't indicate whether values come back as plain strings, code/label pairs, or grouped objects, which matters for an agent that must feed them into search filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the empty schema; the baseline for a parameterless tool applies. The description correctly spends no words on inputs.

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 and resource ("Returns the valid listing-search values") and then enumerates the exact categories returned: property types, ownership types, common areas, currencies, rental modes, amenity names. An agent immediately knows this is a static reference/enumeration lookup, distinct from search_listings or get_listing_details. It stops short of naming the sibling it feeds, so differentiation is by implication rather than explicit contrast.

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?

Usage is implied rather than stated: the phrase "valid listing-search values" signals this should be consulted before constructing a search, but the description never says "call this before search_listings" or specifies any conditions or exclusions. With clear siblings named search_listings and check_availability, an explicit routing sentence would have been cheap and valuable.

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.