Skip to main content
Glama
Sign In

BKK Radar

by com.bkkradar
OverviewDiscussionsAdmin

Median prices of an area

area_stats
Read-onlyIdempotent

Median rent or sale price and number of listings for one BTS/MRT station (within 1 km), one line, or one district or neighbourhood of Bangkok, overall and by bedrooms. Use it to tell whether a price is fair. Returns the bkkradar.com page.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the titles and links: en, fr, th, ja (Japanese) or zh (simplified Chinese). Use the user's language.en
lineNoLine code or name ("BTS-SUK", "BTS Sukhumvit", "MRT Blue"), or a whole network: "BTS", "MRT".
typeNorent (monthly price) or sale (total price).rent
stationNoBTS/MRT station name or code, e.g. "Asok", "Phrom Phong", "BTS-CEN".
bedroomsNoAlso give the median for this number of bedrooms; 0 = studio, 3 or more = the 3+ group.
districtNoDistrict (khet) or neighbourhood: "Watthana", "Sathorn", "Thonglor", "Ari".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's main added value is scope: station results within 1 km, area-level aggregation, and bedroom breakdown. It also notes that it returns the bkkradar.com page, though the return format remains somewhat vague.

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 description is appropriately short and front-loads the resource and scope. The final sentence about returning the bkkradar.com page is useful but slightly underspecified.

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?

Given the rich annotations and fully described schema, the description covers the core purpose, scope, and output content well enough to call the tool. It could do more to explain the returned page or how area selectors interact, especially since there is no output schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning by framing station, line, and district/neighbourhood as alternative area selectors and noting the 1 km station radius. It does not clarify whether multiple area selectors are mutually exclusive or how defaults are applied.

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 states a specific resource and scope: median rent/sale price and listing count for a Bangkok station/line/district, overall and by bedrooms. It is clear enough to distinguish from listing search tools, but it does not explicitly name or contrast with its siblings.

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 clear use case: 'Use it to tell whether a price is fair.' However, it does not explain when to prefer it over search_condos or get_listing, nor does it state exclusions.

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

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