Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

列出在租楼盘

list_release_properties

菜单 2、业务楼盘目录。区→商圈→楼盘逐级浏览。无参返回行政区总览overview;选区/商圈后为properties,每页最多10个楼盘。原样展示display_text,保留换行。仅明确下一页续查。不修改需求,无需session_token,不受 search_ready 门禁限制。不返回具体房源;仅本页有房楼盘创建浏览会话。listing_count=0表示发布范围内暂无可展示房源,不承诺有房。primary_layout/rent_range缺失写待运营补充,不推断。具体楼盘在租房源用search_listings(property_name=单个楼盘名称)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_release_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNooverview区域总览;properties楼盘分页。有区/商圈默认properties,否则overview;明确看全部用properties
cursorNo仅明确下一页沿原view、区/商圈传上次pagination.next_cursor;每轮一页,不自动翻完
districtNo所选区名或编码,如朝阳、110105;不修改需求
business_districtNo所选商圈名称,包含匹配;可结合district,无匹配不放宽

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 only say readOnlyHint=false and destructiveHint=false; the description explains why a write non-read operation exists by disclosing that a browsing session is created only for properties on the current page that have listings. It adds further behavioral facts absent from annotations: listing_count=0 means nothing showable in the release scope and is not a promise of availability, missing primary_layout/rent_range must be written as pending-ops rather than inferred, and display_text must be shown verbatim with line breaks preserved.

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 text is front-loaded with the drill-down model and then packs the output/behavior rules into short clauses, with no filler sentences. It is dense to the point of reading as a run-on list of rules, but each clause carries actionable information for a no-parameter tool with several conditional modes.

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?

There is no output schema, yet the description specifies the two response shapes (overview vs properties), the pagination field (pagination.next_cursor), the display_text rendering requirement, and the meaning of listing_count=0 and of missing fields. For a 4-parameter, all-optional browse tool this covers everything an agent needs to call and interpret it.

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 description coverage is 100%, so the baseline would be 3, but the description adds real semantics: the view defaulting rule (properties when a district/business district is present, otherwise overview) and the page-size cap of 10, plus the constraint that cursor advances one page only along the original view and district context.

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 names the resource and the browsing model concretely: a district → business-district → property drill-down that returns either an overview or a paginated property list (max 10 per page). It also names search_listings(property_name=...) as the tool for unit-level listings, which keeps it distinct from unit search. It stops short of contrasting with the sibling search_release_properties, so the browse-vs-keyword-search distinction must be inferred.

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?

Explicit routing rules are given: no parameters yields the district overview, selecting a district/business district yields properties, and cursor is passed only when the user explicitly asks for the next page. It also states negative guidance that matters for an agent pipeline — do not modify the demand, no session_token needed, and not gated by search_ready — plus a pointer to search_listings for a specific property.

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.