Skip to main content
Glama

RentPro Beijing Premium Rental Consultant

查看房源详情

get_listing_detail
Read-only

获取一套当前可展示挂牌的客户可读详情。默认返回完整详情;通过 include 按需返回 core、price、photos、notes、property、semantic、transport 或 surrounding。只能使用 search_listings/search_listings_by_demand 返回的真实 listing_id/listing_ref 调用;不要向客户展示 listing_ref、来源、置信度、证据、治理状态或更新时间,没有可靠事实时说明待确认,不编造。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listing_id": "<listing_id>"
    },
    "name": "get_listing_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNo按需返回:core、price、photos、notes、property、semantic、transport、surrounding;不传则返回完整详情
listing_idYes房源 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 readOnlyHint/openWorldHint, it discloses the default full-detail payload, the include-based subsetting, and a full set of client-facing disclosure rules (hide listing_ref, source, confidence, evidence, governance status, update time; say 待确认 rather than fabricate). That is real behavioral context an agent cannot get from annotations or schema.

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?

A single dense paragraph that is front-loaded with purpose, then include behavior, then call constraints, then disclosure policy. Every clause carries weight, though the run-on sentence structure makes the disclosure rules easy to skim past.

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?

No output schema exists, so the description should convey more about return shape; it names section categories and the hiding rules but not the response envelope or what a full-detail payload contains. For an open-world read tool this leaves the agent partly guessing about the result.

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 coverage is 100% and the include values plus 不传则返回完整详情 are already in the schema description, so the description largely restates them. It confirms rather than extends parameter meaning, which is the baseline 3 case.

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?

States a specific verb and resource ('获取一套...挂牌的...详情') with scope qualifiers: only currently displayable listings and client-readable detail. That is enough to distinguish it from the search_* siblings, though it never explicitly contrasts with them.

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?

Gives a hard precondition (only call with real listing_id/listing_ref returned by search_listings/search_listings_by_demand), which routes the agent from search to detail. No explicit when-not-to-use beyond that, and no mention of whether repeated calls or bulk use are appropriate.

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.