Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

确认租房需求

confirm_rental_demand

确认租房需求版本。推荐只传 session_token;如传 demand_id,必须同时传同一需求的 session_token。仅允许确认满足当前字段目录必填规则的版本,默认物业类型、租金预算、地段位置、居室;以 search_ready 为准。

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

Input Schema

NameRequiredDescriptionDefault
demand_idNo需求 ID
version_noNo要确认的版本号,可选;不传则确认当前版本
mutation_idNo本次确认幂等键;宿主重试同一次写入时必须复用
session_tokenNo匿名会话令牌
consultation_idNo沿用系统咨询 ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, open-world, non-destructive write; the description adds the real behavioral context: a precondition gate on required-field completeness, the 'search_ready' criterion, and the session_token/demand_id coupling. It does not say what state transition results or how a rejected confirmation surfaces, keeping it below 5.

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?

Three dense sentences, front-loaded with purpose and then the calling rules, with no filler. The clause '默认物业类型、租金预算、地段位置、居室' is slightly ambiguous in how it relates to the required-field rule, which costs a point.

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 five-parameter mutation with no output schema and no required fields, the description covers eligibility and parameter coupling well but leaves out what confirmation actually produces (whether the demand becomes searchable, what changes on failure). That gap matters because annotations alone cannot convey 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 coverage is 100%, so the baseline is 3; the description exceeds that by documenting a cross-parameter constraint the schema cannot express (demand_id requires a matching session_token) and by steering callers toward the session_token-only form. version_no's default is already in the schema, so that sentence adds nothing new.

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+resource pair ('确认租房需求版本' / confirm a rental demand version), which is clearly distinct from siblings like update_rental_demand or start_rental_demand. It does not explicitly name any sibling as an alternative, so it stops short of a 5.

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?

It gives a concrete recommendation ('推荐只传 session_token') plus a hard rule for the demand_id path, and states the eligibility gate: only versions meeting the current field catalog's required rules can be confirmed. What is missing is any explicit comparison to alternative tools for changing demand state.

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.