Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

按需求搜索在租房源

search_listings_by_demand

按同一持久化需求搜索,结果每页一个楼盘并完整返回该楼盘的匹配挂牌,不按套数截断。仅用户明确回复“下一个楼盘”才沿原需求版本、排序和身份传next_cursor。推荐只传session_token;demand_id须带同需求令牌,未齐不搜索。原样展示display_text:有效期→同版本demand_summary→全量统计→本页楼盘资料、demand_editor→本楼盘全部挂牌。摘要保留status_label、仅记录和不限条件,零结果仍有摘要及编辑入口。total等统计全量,listings/property_groups仅本页;需求或房源变化停止翻页,不自动查完。无排名比较。

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": "search_listings_by_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo排序:match、newest、price_asc、price_desc。默认 match
cursorNo仅用户明确回复“下一个楼盘”时传本次pagination.next_cursor;沿用session_token、需求版本和排序,一次返回下一楼盘全部挂牌;条件变化后重查,不自动翻页
demand_idNo需求 ID
version_noNo需求版本号,可选
session_tokenNo匿名会话令牌
consultation_idNo沿用系统咨询 ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond annotations, the description discloses pagination semantics (one property per page, full listings not truncated), stopping rules when demand or listings change, full-scope statistics vs. page-scoped listings, and zero-result summary behavior. It does not explain why readOnlyHint is false despite being a search operation, but the behavioral detail is otherwise rich.

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?

The description is dense and front-loads the core purpose, but it reads as a single long paragraph with compressed instructions. The arrow sequence for display_text is functional, yet overall structure could be improved with clearer separation between tool behavior and output presentation rules.

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 complex paginated tool with no output schema, the description explains the return structure (display_text ordering, full-scope statistics, page-scoped listings), zero-result behavior, and pagination stop conditions. Some completeness gaps remain, such as authentication requirements and error behavior, but the core calling context is well covered.

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 schema already defines sort options and cursor. The description adds meaning beyond the schema by recommending session_token alone, requiring demand_id to be paired with the same demand token, and specifying that cursor must only be sent upon explicit user request, which is useful operational guidance.

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 opens with a specific verb and resource ('按同一持久化需求搜索' — search listings by the same persistent demand) and clarifies that results paginate one property group per page with all matching listings. This distinguishes it from a generic listing search, though it does not explicitly name the sibling tool search_listings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear conditions for using next_cursor (only when the user explicitly says 'next property') and parameter pairing rules ('推荐只传session_token', demand_id requires the same demand token). However, it never states when to use this tool instead of search_listings or get_rental_demand, leaving tool selection guidance incomplete.

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.