Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

开启租房咨询

start_rental_demand
Idempotent

用户独立选择菜单数字1后启动咨询,或已启动后明确重领空表时调用。每次返回 template_mode=blank_intake,只发 intake_template,不附定制页提示/链接/按钮,该响应不返回 demand_editor;重复和重试同样适用。已有需求再选1用 render_rental_demand_template。本工具只创建或续接原草稿,不清空、不搜索、不带入启动前输入。

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

Input Schema

NameRequiredDescriptionDefault
mutation_idNo本次启动幂等键;宿主重试同一次写入时必须复用
source_agentNo已知客户端。
session_tokenNo匿名会话令牌;同一宿主会话后续继续使用,首次可不提供
source_channelNo已知宿主渠道。
consultation_idNo沿用系统咨询 ID。
source_campaignNo已知活动批次。
host_instance_idNo已知宿主实例/租户范围。
host_conversation_idNo真实宿主聊天 ID;未知省略。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint=true, destructiveHint=false, openWorldHint=true), the description discloses the exact response shape: always template_mode=blank_intake, only intake_template is sent, no custom page hints/links/buttons, and demand_editor is omitted. It also confirms repeat and retry behave identically and that existing drafts are neither wiped nor supplemented, which is exactly the kind of side-effect context an agent needs before calling a write tool.

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?

Sentences are front-loaded with the trigger, then the response contract, then the alternative route, then the non-behaviors, and nothing is padding. It is, however, a dense semicolon-joined block that takes a careful read to separate the trigger rule from the response contract.

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?

With eight optional parameters and no output schema, the definition still conveys trigger, response payload, idempotent/repeat behavior, and explicit non-actions, which is everything needed to call it correctly. No material gap remains for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all eight parameters including mutation_id and session_token are already documented in the schema. The description adds no meaning on parameter usage or which of the optional fields matter for this call, so the baseline 3 applies.

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 description names a concrete action (start/continue a rental-demand consultation and return a blank intake template) and ties it to a specific trigger moment, distinguishing it explicitly from render_rental_demand_template. An agent can tell what this tool produces (template_mode=blank_intake, intake_template only) without opening the schema.

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?

It gives both the when (user independently picks menu item 1, or explicitly re-requests a blank form after starting) and the when-not with a named alternative (if a demand already exists and 1 is chosen again, use render_rental_demand_template). It also states the boundaries: no clearing, no searching, no carrying over pre-start input.

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.