Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

查看需求清单模板

render_rental_demand_template
Read-onlyIdempotent

查看当前需求,不自动搜索。无已填条件返回 template_mode=blank_intake 和完整空白 template,无 demand_editor,不补定制页提示、链接或按钮。有实际条件(含部分填写、不限、否定或网页筛选)返回 template_mode=saved_demand 和有效 demand_editor,在内容外单独展示编辑入口。按内容判断。推荐只传 session_token;传 demand_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": "render_rental_demand_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
demand_idNo需求 ID
version_noNo需求版本号,可选
session_tokenNo匿名会话令牌
consultation_idNo沿用系统咨询 ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which only declare read-only/idempotent/open-world), the description discloses the two conditional return modes, template_mode=blank_intake vs saved_demand, the presence or absence of demand_editor, and that no extra hints, links, or buttons are injected. That is exactly the behavioral context an agent needs and cannot get from structured fields.

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?

The purpose is front-loaded and each clause carries a rule, so there is little outright waste. The middle sentences are dense and run together, which slightly hurts readability but does not add bloat.

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?

For a read-only, zero-required-parameter tool with no output schema, the description covers conditional outcomes and the token constraints well. It leaves the internal shape of the returned template unexplained, but nothing essential for correct invocation is missing.

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 still adds meaning by recommending session_token alone and warning that demand_id must be accompanied by the matching demand token. That constraint is not visible in the schema.

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 states a specific verb+resource: 查看当前需求 (view the current demand) rendered as a template, with the explicit qualifier 不自动搜索. It is distinguishable from get_rental_demand, though it never names a sibling to contrast with, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful exclusions — no automatic search, no history browsing — and a parameter recommendation (只传 session_token), but it never says when to pick this over get_rental_demand or get_rental_demand_filters. The guidance is implied rather than explicit routing.

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.