Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

读取租房需求

get_rental_demand
Read-onlyIdempotent

读取当前租房需求、search_ready、缺失必填项及 demand_editor 授权编辑链接。网页保存后必须用原 session_token 读取最新需求,齐全再自动调用 search_listings_by_demand,未齐继续收集。也可为原需求刷新过期链接,不创建另一份需求。如传 demand_id,必须同时传同一需求的 session_token。

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

Input Schema

NameRequiredDescriptionDefault
demand_idNo需求 ID
session_tokenNo匿名会话令牌
consultation_idNo沿用系统咨询 ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the returned payload includes search_ready and missing-field state, link refresh is non-creating, and demand_id must be paired with the session_token of the same demand. It does not discuss token expiry semantics or failure modes, keeping it short of a 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?

Front-loaded with what is returned, then the workflow rules, then the parameter constraint — a logical order with no filler. It is dense and slightly run-on in the middle clause about auto-calling search_listings_by_demand, but every sentence carries operational information.

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 no output schema, the description compensates by enumerating the return contents (demand, search_ready, missing fields, edit link), which is what an agent needs to branch on. The workflow handoff to search_listings_by_demand is covered; only edge cases such as invalid or expired session_token handling are left implicit.

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, but the description adds a genuine cross-parameter constraint not expressible in the schema: if demand_id is supplied, session_token for that same demand is mandatory. It also implies session_token is the anonymous session identity used for re-reads, adding meaning beyond the terse schema labels.

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?

States a specific verb (读取/read) and resource (当前租房需求) and enumerates exactly what is returned: the demand itself, search_ready, missing required fields, and the demand_editor authorized edit link. This is clearly distinguishable from siblings like update_rental_demand or search_listings_by_demand, which the description names as downstream steps.

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?

Gives explicit when-to-use and sequencing rules: after a web save, re-read with the original session_token, and only auto-call search_listings_by_demand once the demand is complete, otherwise keep collecting. It also states the negative case — refreshing an expired link for an existing demand must not create a second demand — and the pairing constraint for demand_id plus session_token.

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.