Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

按条件筛选在租楼盘

search_release_properties

按楼盘条件筛选当前 MCP 发布范围中的业务楼盘,而不是挂牌房源。filters 每项含 filter_code、operator、value;多个条件默认 AND。支持泳池、健身房、会所、地暖(eq,布尔值)、标准层高(gt/gte/lt/lte/eq,单位米)、交付日期(日期比较使用 YYYY-MM-DD;within_years 使用整数年数)、明确环线区域/沿线(property_ring.zone,必须使用目录值)和户型存在型条件:house_type.is_5plus_bedroom=true、house_type.is_300plus_sqm=true、house_type.bedroom_count(室数)、house_type.area(单值面积,㎡)及 house_type.elevator_per_household='1梯1户'。实体条件 property_entity.mall_within_m、property_entity.supermarket_within_m、property_entity.metro_within_m 只接受 lt/lte,value 为大于0且不超过50000的米数;距离是登记点间直线距离,非步行时间,未查到匹配计入未知而不是确认没有配套。不接受原始 ring 字段或“三环附近”等模糊值。户型条件必须由同一真实户型满足;面积区间、缺失或冲突不命中且可能计入未知;一梯一户不等同于私密或管理严格。字段与实时可用权限以 get_property_filter_catalog 为准。返回区→商圈→楼盘、匹配事实及命中户型摘要,不创建需求、不返回挂牌;为房源入口创建临时浏览会话。

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": {
      "filters": "<filters>"
    },
    "name": "search_release_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersYes楼盘条件数组;每项含 filter_code、operator、value。多个条件默认全部满足(AND)。先读取 get_property_filter_catalog,不要自行猜字段编码。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, which for a search tool would normally be confusing; the description resolves that by explaining it creates a temporary browsing session for the listing entry point. Beyond that it discloses multiple-conditions-default-AND semantics, that distances are registered-point straight-line distances rather than walk times, and the crucial 'unknown vs confirmed absent' behaviour for unmatched distances and missing/interval/conflicting area values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and nearly every sentence carries real constraint information, so little is wasted. However it is delivered as one dense, unstructured block mixing return shape, caveats and per-filter syntax, which makes it hard to scan; the return-format sentence is buried at the very end.

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 single nested-array parameter with no output schema, it covers the return shape (区→商圈→楼盘, match facts, house-type summary), the unknown-value semantics and the catalogue prerequisite. The remaining gap is the absence of any guidance on choosing between this tool and list_release_properties for published-property queries.

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 coverage is 100%, but the schema only defines the generic filter_code/operator/value triple; the description supplies the actual vocabulary — supported amenity flags, height and delivery-date operators and units, the ring zone catalogue requirement, the house-type existence conditions, and the lt/lte-only 0–50000 m constraint on entity-distance filters. This is meaning the schema cannot convey.

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 opening clause states a specific verb and resource (filter business 楼盘 in the current MCP publish scope) and explicitly excludes the nearest confusion (挂牌房源 / listings), which is the sibling search_listings' territory. An agent can tell this apart from listing search without opening any 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?

It gives an explicit prerequisite and routing instruction: read get_property_filter_catalog first and never guess field codes. It also states exclusions ('不创建需求、不返回挂牌') and the side effect of creating a temporary browsing session. The one gap is that it never distinguishes this from the sibling list_release_properties, which also returns published properties.

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.