Wehome

Search Wehome stays

search_accommodations

Read-onlyIdempotent

Use this when the user wants to find a homestay or short stay in South Korea. Filters by area or theme, dates, adult guests, and nightly price in KRW, and returns matching Wehome listings with price, rating, and a link to the listing. Only covers South Korea. Does not make a reservation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "search_accommodations"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Pagination page number (starts at 1)
`sort`	No	Sort order: recommend, price_asc (low to high), price_desc (high to low)	recommend
`checkin`	No	Check-in date in YYYY-MM-DD format. Give together with checkout to get only available stays.
`keyword`	Yes	Area, station, or theme in Korean or English (e.g., 'Hongdae', 'Busan', 'Jeju', 'Hanok')
`checkout`	No	Check-out date in YYYY-MM-DD format, after checkin.
`num_guests`	No	Number of guests
`price_range`	No	Semicolon-separated min and max price per night in KRW (e.g., '50000;150000')

Output Schema

Name	Required	Description	Default
`total`	Yes	Number of matching listings
`listings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/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, and the description adds meaningful boundaries on top: geographic scope, the fact that it does not book, and the currency (KRW). It stops short of describing pagination behavior or result caps, which would be the remaining behavioral gap.

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?

Four short sentences with zero waste: trigger condition first, then filters, then return shape, then scope limits. Front-loaded and each sentence carries distinct information.

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?

An output schema exists, so return values need not be re-explained; the description still summarizes the key fields (price, rating, link). For a read-only, single-required-parameter search with full schema coverage and explicit scope limits, nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, so the baseline is 3 by rule. The description adds only small deltas over the schema – 'nightly price in KRW' and 'adult guests' – while the rest of the filter list merely restates documented parameters.

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?

States a specific verb and resource ('find a homestay or short stay in South Korea') and enumerates the filter dimensions, so the agent knows exactly what the tool retrieves. It does not name or differentiate itself from the sibling get_smart_suggestions, which keeps it 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?

The opening 'Use this when the user wants to find a homestay or short stay' gives a clear triggering condition, and the closing 'Only covers South Korea. Does not make a reservation.' sets explicit exclusions. No alternative tool is named, so it falls short of the 5 bar for when-not/alternatives routing.

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

All Wehome tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?