BKK Radar

Condos near a place

nearby_condos

Read-onlyIdempotent

Condos around a point in Bangkok, such as an office, a school, a residence or a station, given as lat/lng or as a place name or address. Same filters as search_condos plus radius_km, sorted by distance or by walk to a station. Returns bkkradar.com links.

Input Schema

Name	Required	Description	Default
`lat`	No	Latitude of the point (Bangkok area).
`lng`	No	Longitude of the point (Bangkok area).
`lang`	No	Language of the titles and links: en, fr, th, ja (Japanese) or zh (simplified Chinese). Use the user's language.	en
`sort`	No	distance (closest to the point first) or station_walk (closest to a station first).	distance
`type`	No	rent (monthly price) or sale (total price).	rent
`limit`	No	Listings to return, 20 by default, 50 at most.
`place`	No	Address or place in Bangkok instead of lat/lng: an office, a school, a station, a residence.
`bedrooms`	No	Exact number of bedrooms; 0 = studio.
`max_price`	No	Maximum price in THB (per month for rent).
`min_price`	No	Minimum price in THB.
`radius_km`	No	Distance from the point, at most, in km (straight line).
`min_bedrooms`	No	At least this many bedrooms.
`min_size_sqm`	No	Living area, at least, in m².
`property_kind`	No	Kind of property; any for all.	condo
`max_lease_months`	No	Rentals that accept a lease this short, at most, in months (1 to 6): 6 for a DTV stay of 180 days. Prices are then that lease's monthly rent when the post gives it, often higher.
`max_walk_minutes`	No	Walk to the listing's nearest BTS/MRT station, at most, in minutes (straight line at 80 m a minute). With a station or line and no value: 12 (1 km).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / max_lease_months

Added value: +{
+  "description": "Rentals that accept a lease this short, at most, in months (1 to 6): 6 for a DTV stay of 180 days. Prices are then that lease's monthly rent when the post gives it, often higher.",
+  "maximum": 6,
+  "minimum": 1,
+  "type": "integer"
+}

Changed2 schema fields changedOct 23, 2026

changedInput schema / properties / lang / description

Previous value: -"Language of the titles and links: en, fr or th. Use the user's language."New value: +"Language of the titles and links: en, fr, th, ja (Japanese) or zh (simplified Chinese). Use the user's language."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "fr",
-  "th"
-]New value: +[
+  "en",
+  "fr",
+  "th",
+  "ja",
+  "zh"
+]

First observedOct 21, 2026

TDQS

A4.2/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, so the safety profile is covered. The description adds valuable behavioral context: that sorting is either by distance or walk to a station, and that results are bkkradar.com links. It doesn't detail pagination or result shape, but that's secondary for a read-only tool with annotated safety.

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?

Two tight sentences with no filler. The core purpose and input modes are front-loaded, followed by the differentiating filter and return-format detail in the second sentence.

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?

For a 16-parameter proximity-search tool with full schema coverage and clear annotations, the description covers the essential: input modes, filter relationship to search_condos, sorting, and return format (links). It lacks detail on result structure or pagination, but with no output schema and a low-risk read operation, the description is sufficiently complete.

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% and all 16 parameters—including radius_km and sort—are well documented in the schema. The description reiterates the radius and sort concepts but adds no additional semantics or format details beyond what the schema already provides. Baseline 3 is appropriate.

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?

States a specific verb-and-resource ('Condos around a point in Bangkok') with scope (lat/lng or place name/address) and explicitly distinguishes itself from its sibling by noting it applies the 'same filters as search_condos plus radius_km'. An agent can tell exactly what it returns and how it differs from search_condos without opening a schema.

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?

Clearly establishes the use case—proximity search around a point—and names search_condos as the filter baseline, which implies the alternative for non-geo searches. No explicit when-not or exclusion is stated, but the context is unambiguous for selecting this tool.

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

All BKK Radar 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?