Back to Details

gezgin

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Gezgin

Gezgin

Use the tools supplied by the declared Gezgin MCP dependency to complete the user's travel or community goal.
使用已声明的Gezgin MCP依赖提供的工具来完成用户的旅行或社区目标。

Keep the runtime boundary

遵守运行时边界

  • Treat the live MCP catalog, schemas, metadata, and results as authoritative.
  • Use the skill only for tool selection, sequencing, clarification, and presentation. Leave live data, identity, access, account entitlements, controlled-action policy, and runtime failures to MCP.
  • For a connected workflow, call 
    get_account_capabilities
    before other connected tools. Let the native client establish or extend the connection. Never ask the user for credentials, construct authentication headers, or call the MCP endpoint through raw HTTP.
  • Use only tools available in the current catalog. If a named tool is unavailable, stop that workflow and explain which capability is missing without inventing a substitute.
  • Call the smallest set of tools needed for the current request. Re-read state when a later step depends on current server-owned values.
  • 将实时MCP目录、模式、元数据及结果视为权威来源。
  • 本技能仅用于工具选择、流程排序、需求澄清及结果展示。实时数据、身份验证、访问权限、账户权益、受控操作策略及运行时故障处理均交由MCP负责。
  • 对于关联工作流，在调用其他关联工具前先调用
    get_account_capabilities
    。由原生客户端建立或扩展连接。切勿向用户索要凭证、构造认证头或通过原始HTTP调用MCP端点。
  • 仅使用当前目录中可用的工具。若指定工具不可用，终止该工作流并说明缺失的功能，切勿自行替代。
  • 调用完成当前请求所需的最少工具集。当后续步骤依赖当前服务器拥有的值时，重新读取状态。

Route the request

路由请求

  • Read destination research for location discovery, comparisons, shortlists, and comparison presentation.
  • Read profile and community for profile context, profile changes, member discovery, follows, and current presence.
  • Read event workflows for public event discovery, meetup drafts, launch, invitations, participation, and organizer actions.
  • Read every relevant reference when a request crosses domains, then compose one coherent workflow instead of repeating the same read.
  • 如需进行地点发现、对比、候选清单及对比展示，请阅读目的地研究。
  • 如需处理个人资料背景、资料修改、成员发现、关注及当前状态，请阅读个人资料与社区。
  • 如需进行公开活动发现、聚会草稿创建、发布、邀请、参与及组织者操作，请阅读活动工作流。
  • 当请求涉及多个领域时，阅读所有相关参考文档，然后构建一个连贯的工作流，避免重复阅读。

Clarify and present

澄清与展示

  • Ask a focused question only when the answer would select a different tool, target, or outcome. Resolve names to server-returned references whenever possible instead of asking the user for opaque identifiers.
  • Do not guess missing facts, tool results, references, availability, or freshness. State what is unknown when the tools do not resolve it.
  • Preserve source attribution, freshness, and uncertainty returned by Gezgin. Distinguish tool-backed facts from recommendations or synthesis.
  • Answer in the user's language unless they request another language. Lead with the useful result, then summarize any completed or still-pending connected action.
  • 仅当答案会影响工具、目标或结果的选择时，才提出针对性问题。尽可能将名称解析为服务器返回的引用，而非向用户索要不透明标识符。
  • 切勿猜测缺失的事实、工具结果、参考资料、可用性或时效性。当工具无法解决问题时，说明未知信息。
  • 保留Gezgin返回的来源归因、时效性及不确定性。区分工具支持的事实与建议或综合内容。
  • 使用用户的语言作答，除非用户要求其他语言。先展示有用的结果，再总结已完成或待处理的关联操作。