Skip to main content
Glama
manganate006

homeexchange-mcp

by manganate006
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

he_search_homes

Search for home exchange listings with filters for location, guest count, amenities, and availability. Returns home ID, location, bedrooms, rating, owner, and cover image.

Instructions

Search for homes/properties. Returns slimmed results (id, location, bedrooms, rating, owner, cover image).

⚠️ IMPORTANT: If you pass calendar.date_ranges in filters, results are ALREADY filtered by availability — do NOT call he_get_calendar on each result, it is redundant and wastes tokens. Only call he_get_calendar when you need the full availability breakdown of a specific home.

Full example with all filter categories: { "location": { "bounds": { "sw": { "lat": 36.0, "lon": -9.5 }, "ne": { "lat": 43.8, "lon": 4.3 } } }, "guests_nb": 4, "home": { "type": "home", "size": { "bedrooms": 2, "bathrooms": 1 }, "amenities": ["swimming-pool", "a-c", "wifi"], "surrounding": ["seaside"], "is_primary": true, "is_private_room": false, "exclude_animals": ["cat", "dog"] }, "calendar": { "date_ranges": [{ "from": "2026-08-05", "to": "2026-08-19" }] }, "exchange_type": "reciprocal", "filters": ["home-verified", "response-rate-above-threshold"] }

Filter reference

location: bounds {sw/ne with lat/lon} or location_id (Jawg polygon)

home.type: "home" (maison) | "flat" (appartement)

home.is_private_room: false (logement entier) | true (chambre privée)

home.is_primary: true (résidence principale) | false (résidence secondaire)

home.surrounding (array): "countryside" | "mountains" | "seaside" | "lakes" | "cities" | "villages" | "isolated" | "island"

home.amenities (array):

  • Essentials: "heating-system" | "dishwasher" | "washing-machine" | "dryer" | "bathtub" | "tv" | "wifi" | "electric-car-plug"

  • Comfort: "a-c" | "elevator" | "parking-space" | "jacuzzi" | "fireplace" | "gym" | "garden" | "balcony-terrace" | "swimming-pool" | "public-transit-access"

  • Kids: "baby-bed" | "kids-toys" | "playground" | "baby-gear" | "secured-pool"

  • Work: "dedicated-workspace" | "high-speed-connexion"

  • Accessibility: "disabled-access" | "children-welcome" | "pets-welcome" | "smokers-welcome"

home.exclude_animals (array): "cat" | "dog" | "other"

home.eco_level: 4 (maisons durables uniquement)

exchange_type: "available" (all) | "reciprocal" | "guest-wanted" (GuestPoints only)

filters (array): "home-verified" | "response-rate-above-threshold" ← prefer this over min_response_rate param

calendar.date_ranges: [{ "from": "YYYY-MM-DD", "to": "YYYY-MM-DD" }] calendar.duration: { "kind": "week-end" | "week" | "month" }

guestpoint_range: { "min": 0, "max": 250 } (GP per night)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (default: 20, max: 50)
offsetNoPagination offset (default: 0)
filtersYesSearch query filters (location, calendar, home, guests_nb, filters)
min_response_rateNoMinimum owner response rate % to include (0-100, client-side filter)

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that 'min_response_rate' is a client-side filter, warns about token waste if he_get_calendar is called unnecessarily, and notes that results are slimmed. However, no mention of idempotency or side effects, but as a read operation it is sufficient.

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?

Description is long but well-structured: a header, a bold warning, a full example, and a detailed filter reference. It is front-loaded with key purpose and warning. Slightly verbose but every section adds value.

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

Completeness5/5

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

All 4 parameters are explained, including pagination limits. Return format is described (slimmed results with fields). Without output schema, the description compensates by listing returned fields. The filter reference covers all nested objects. Complete for a search tool.

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

Parameters5/5

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

Schema has 100% description coverage, but the description adds extensive meaning beyond schema. For example, schema says 'filters' is 'Search query filters', but the description gives a complete filter reference with all subfields, values, and examples, significantly enhancing agent understanding.

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?

The description states 'Search for homes/properties' and specifies the return of 'slimmed results' with fields listed. It distinguishes itself from siblings like 'he_get_calendar' by warning against redundant calls, clearly separating its purpose.

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?

Explicitly states when to use and when not to use: 'If you pass calendar.date_ranges in filters, results are ALREADY filtered by availability — do NOT call he_get_calendar'. Provides a full example and filter reference, guiding proper usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/manganate006/homeexchange-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server