zhini_get_customer_profile按客户 UID 获取客户资料和标签，用于确认客户身份、来源、负责人、联系方式、备注和标签。适用于客服回复前、销售跟进前、复盘客户历史前。边界：只读查询，不修改客户资料、备注、负责人或标签。前置：如果用户只给姓名/手机号/微信号，先用 zhini_search_customers 找 uid；如果已经有 uid，直接调用本工具。后续：需要聊天上下文时调用 zhini_fetch_messages。
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | 知你侧客户 UID。通常由 zhini_search_customers 返回，也可由会话数据中的 uid 字段提供。 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
由于没有提供注解，描述承担了揭示行为特征的全部责任。描述明确指出这是只读查询，不会修改客户资料、备注、负责人或标签，这界定了工具的副作用范围。虽然没有详细说明权限要求或失败模式，但对只读性质的说明已经足够清晰。
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
描述简洁紧凑，没有冗余信息。每一个句子都承载了具体价值：用途、使用场景、只读边界、前置条件、后续步骤。信息组织逻辑清晰，先说明做什么，再说明何时用，最后说明如何衔接其他工具。
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
描述在现有上下文中已经较为完整：明确了输入参数、使用场景和后续工具。虽然没有提供输出格式细节，但考虑到没有输出 schema，且工具名称明确表明是获取客户资料，代理可以合理预期返回内容。结合兄弟工具列表，整体上下文足以支持正确调用。
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
唯一的参数 uid 在描述中得到了充分解释，说明了其含义（知你侧客户 UID）和常见来源（zhini_search_customers 返回或会话数据提供），帮助代理理解如何获取该参数。参数描述与 schema 完全匹配，无遗漏。
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
描述明确说明了工具用途：按客户 UID 获取客户资料和标签，并列举了包含的信息类型（身份、来源、负责人、联系方式等）。还提供了典型使用场景，帮助代理理解何时调用此工具。
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
描述给出了明确的使用前置条件：当只有姓名/手机号/微信号时，应先用 zhini_search_customers 查找 uid，这有助于代理正确选择工具。还提到了后续可调用 zhini_fetch_messages 获取聊天上下文，形成了完整的使用流程。虽然没有明确列出不适用场景，但结合兄弟工具列表，已能指导代理做出选择。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.