Skip to main content
Glama

SalonRenter for Muse

search_listings

Search published salon suites, booths, chairs, and entire salons. city or lat and lng are required. Results sort ok prices first; unusual and invalid prices come last. weeklyPrice is the low end of the posted price converted to USD per week, and is null when the price is invalid. priceQuality is ok, unusual, or invalid (null when no price is posted). Treat unusual or invalid prices as unverified: do not quote them as typical, pass along priceNote, and suggest confirming with the owner. likelyJobAd marks job posts, which are not rentals.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lngNo
cityNo
limitNo
stateNo
offsetNo
amenitiesNo
listingTypeNo
radiusMilesNo
maxWeeklyPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses sort order (valid prices first, unusual/invalid last) and the meaning of output fields (weeklyPrice normalization to USD/week, priceQuality states, likelyJobAd for job posts). Gaps remain around pagination behavior (limit/offset are capped at 50/9007199254740991 in the schema but the description says nothing about defaults or result windowing), which is why this is not a 5.

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 definition is front-loaded with purpose and location requirements, and each subsequent sentence covers a distinct output-semantics concern that has no other documentation channel. Phrasing is occasionally compressed to the point of ambiguity ('Results sort ok prices first'), but there is little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter search tool with no annotations and no output schema, the description admirably covers return-value semantics but under-serves the input surface. An agent still cannot tell what amenities accepts or how radiusMiles interacts with city vs lat/lng, and the required-parameter claim conflicts with the schema's empty required list.

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% across 10 parameters, so the description must compensate and only partially does. It clarifies location requirement and the listingType value set, but leaves state, amenities (free-form string, format unspecified), radiusMiles, maxWeeklyPrice, limit, and offset without meaning beyond their names — and most of the prose is spent on output fields rather than 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 opens with a specific verb and resource set: 'Search published salon suites, booths, chairs, and entire salons,' which also maps onto the listingType enum values. It does not explicitly contrast itself with siblings like get_listing or city_rents, so it lands just short of a 5.

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

Usage Guidelines4/5

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

It gives a hard usage constraint ('city or lat and lng are required') and explicit result-handling instructions for low-quality prices ('do not quote them as typical, pass along priceNote, and suggest confirming with the owner'). It offers no when-not-to-use guidance or guidance on choosing between this and sibling retrieval tools.

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