Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

获取房源经理联系方式

get_manager_contact
Read-onlyIdempotent

获取房源经理公开联系方式和填写入口。保存并沿用返回的 session_token;pending 表示尚未写库。仅在主动询问联系方式时调用;明确要求联系、核验或约看使用 request_viewing。

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_manager_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_agentNo已知客户端标识,如 dsh、workbuddy、codex;未知省略,不向客户展示。
session_tokenNo沿用当前对话凭证以关联需求和客资;首次省略。
source_channelNo真实宿主渠道,如 dsh、workbuddy;未知传 mcp,不猜测、不向客户展示。连接头优先;可选兼容旧客户端。
consultation_idNo沿用系统咨询 ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), yet the description still adds value: the caller must persist and reuse the returned session_token, and 'pending' signals the record has not yet been written to the store. It stops short of describing what the contact payload or fill-in entry actually contains.

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 compact sentences ordered as purpose, state handling, then routing decision, with no filler. Density is high — pending and session_token are introduced without much elaboration — but nothing is redundant.

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 lookup with no output schema and full parameter coverage, the description supplies enough: what is returned, the token lifecycle, the pending state meaning, and sibling routing. The only gap is the shape of the returned contact/form entry, which an agent must discover at call time.

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 four parameters are already documented, including the omit-when-unknown rules for source_agent and source_channel. The description only restates the session_token reuse rule, adding little meaning beyond what the schema says about 沿用当前对话凭证.

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 specific verb and resource — retrieving the listing manager's public contact details plus a fill-in entry point — and separates that purpose from the sibling request_viewing by name. An agent can identify the tool's job 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 states an explicit trigger ('仅在主动询问联系方式时调用') and an explicit hand-off rule: when the user asks to be contacted, verified, or to book a viewing, use request_viewing instead. Both the when and the when-not, with the alternative named, are present.

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.