Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

更新租房需求

update_rental_demand

按字段级 patch 更新当前租房需求并生成新版本。推荐只传 session_token;如传 demand_id,必须同时传同一需求的 session_token。先读取 basic_catalog,仅提交允许自然语言录入的字段,未知字段会拒绝。可先保存草稿,以返回的 search_ready 和缺失字段为准;默认必填为物业类型、租金预算、地段位置、居室。null 或 clear_fields 表示清空,复合字段局部修改用嵌套对象;整体替换时在 clear_fields 中列出该字段。

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

Input Schema

NameRequiredDescriptionDefault
patchNo字段级补丁,例如 location/budget/bedrooms/area/must_have/preferred/exclude/pending/weights/clear_fields
statusNo状态:active、paused、archived
confirmNo是否将新版本同时设为已确认版本
demand_idNo需求 ID
input_textNo用户原始修改说明,可选
mutation_idNo本次更新幂等键;宿主重试同一次写入时必须复用
session_tokenNo匿名会话令牌
consultation_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 it discloses that each call creates a new version, that unknown fields are rejected, that drafts are allowed, what the default required fields are, and what the response surfaces (search_ready, missing fields). Slight tension with idempotentHint=false given the mutation_id retry guidance, but that reflects per-call versioning rather than a true contradiction.

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?

Front-loaded with purpose, then workflow, then patch semantics; every sentence carries calling-relevant information. It is dense and slightly clause-heavy in the last sentence but has no filler.

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?

With 8 optional parameters, a nested patch object, and no output schema, the description covers the write workflow, validation rules, clearing semantics, and the return signals an agent needs. The only minor omission is elaboration on status/confirm/consultation_id behavior, which the schema partially covers.

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 baseline is 3, but the description adds real semantics: null or clear_fields means clearing, nested objects mean partial modification of composite fields, and whole-field replacement requires listing the field in clear_fields. It also explains the session_token/demand_id interaction beyond the terse schema text.

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 first sentence states a specific verb and resource (update current rental demand via field-level patch) plus a distinct outcome (generates a new version). That outcome and the patch orientation separate it from confirm_rental_demand and update_rental_demand_filters, though the description never names those siblings 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?

Strong operational guidance: prefer session_token only, pair demand_id with the same demand's session_token, read basic_catalog first, submit only natural-language-eligible fields, draft-first workflow with search_ready as the gate. It does not explicitly say when to choose this over sibling tools like update_rental_demand_filters, which keeps it below a 5.

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.