Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

提交看房咨询

request_viewing
DestructiveIdempotent

提交客户咨询/看房意向到 RentPro 后台。适用于用户愿意留联系方式、希望顾问联系、需要人工核验或对一套/多套房源明确感兴趣时;该工具只创建或补全客资包,不自动承诺预约成功。支持匿名 session_token 续接同一会话;传 demand_id 时必须同时传同一需求的 session_token,服务端会校验归属后再把当前需求版本和快照附到客资。宿主重试同一次提交时复用 mutation_id,避免重复写入。

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

Input Schema

NameRequiredDescriptionDefault
noteNo客户备注,例如预算、其他需求
sourceNo兼容来源字符串,例如 mcp、mcp:workbuddy、mcp:workbuddy:it_seed_user:pilot_2026_09。默认 mcp
lead_idNo已有客资 ID。若之前已创建待补充联系方式客资,再次提交时传入该 ID 进行续填
summaryNo对话需求摘要,例如预算、区域、通勤、硬性要求和已关注房源
demand_idNo当前租房需求清单 ID。传入后自动把当前需求版本和快照附到客资,供房源经理人工核验
listing_idNo主房源 ID,可选
mutation_idNo本次写入幂等键;宿主重试同一次提交时必须复用同一值
source_toolNo触发客资的工具或入口,默认 request_viewing
contact_nameNo联系人姓名或称呼
contact_typeNo联系方式类型:phone 或 wechat
requirementsNo结构化需求快照,例如预算、区域、居室、面积和通勤条件
source_agentNo具体 Agent 或客户端标识,例如 workbuddy、codex、self_agent
contact_valueNo手机号或微信号
session_tokenNo匿名会话令牌。用于同一宿主会话续接匿名咨询;传 demand_id 时必填且必须属于同一需求;未传 demand_id 时可自动生成
preferred_timeNo期望看房时间,例如:明天下午3点
source_channelNo自报宿主或获客渠道,例如 dsh、cursor、workbuddy、it_seed_user;未知不猜。连接头优先于参数,仅用于分析,不用于权限或结算
consultation_idNo沿用系统咨询 ID。
conversation_idNo宿主当前对话 ID,用于把本次客资与原始对话关联
source_campaignNo活动或试点批次,例如 beijing_luxury_pilot_2026_09
host_instance_idNo已知宿主实例/租户范围。
interested_listingsNo感兴趣房源 ID 列表,可包含多个
host_conversation_idNo真实宿主聊天 ID;未知省略。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real side effects: attaching the current demand version and snapshot to the lead, server-side ownership validation of session_token against demand_id, and mutation_id reuse to suppress duplicate writes on host retries. It also states the outcome bound (no guaranteed booking). The gap is that annotations declare destructiveHint=true, yet the description never says what is overwritten when '补全' fills an existing lead via lead_id.

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?

Three sentences, ordered purpose → applicability → operative constraints, with the scope limitation placed early rather than buried. Length is proportionate to a 22-parameter mutation tool, and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex write tool with no output schema, the definition covers intent, side effects and idempotency well but never says what comes back — notably the lead_id an agent would need to reuse for the '续填' continuation flow the description itself describes. The destructive behavior implied by annotations is also unaddressed, leaving a meaningful completeness gap.

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, and the description earns an increment by stating cross-parameter rules the schema documents only locally: demand_id requires a session_token belonging to the same demand, and session_token may be auto-generated when demand_id is absent. These are relational constraints that matter more than any single field's definition.

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 opening sentence pairs a specific verb (提交) with a specific resource and destination (客户咨询/看房意向 → RentPro 后台), and it bounds the outcome ('该工具只创建或补全客资包,不自动承诺预约成功'). That scope statement lets an agent tell it apart from demand/search tools, though no sibling is named explicitly.

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?

The when-to-use conditions are concrete and enumerated: the user is willing to leave contact details, wants an advisor to call, needs human verification, or has clear interest in one or more listings. There is no explicit when-not guidance or named alternative tool, so an agent must infer the negative case.

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.