Skip to main content
Glama

独行录 / opcmenu

主办方:把某个人加进嘉宾阵容

add_activity_guest

【需要登录·主办方】点名请某个人当嘉宾的第一步:把他录进这场的嘉宾阵容,站内用户挂上 userId。 【组合链】search_people(q=名字) 核对是哪一位 → 本工具 → create_guest_invite_link(guestId) → start_conversation / send_message 把链接发给他(发之前念给用户确认)。 【口径/坑】① 缺省 confirmed=false(草稿,不上公开页);只有对方明确答应出席并同意展示,才传 confirmed=true。② 头像让嘉宾在自助卡里自己传。③ 每场最多 30 位。④ 本工具不通知任何人。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes嘉宾姓名 / 昵称(公开页与海报上显示的名字)
titleNo头衔 / 一句话身份,可选
topicNo分享主题,可选
userIdNo站内用户 id(search_people / get_creator 拿到的),外请嘉宾不传
confirmedNo对方已明确答应出席并同意公开展示才传 true,缺省 false
activityRefYes活动 slug 或 id(list_my_activities 的返回里都有)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

在注解已声明写操作、开放世界、非幂等且非破坏性的基础上,额外披露了需要登录且为主办方、缺省 confirmed=false 不上公开页、仅在对方明确同意并同意展示时才传 true、每场最多 30 位、本工具不通知任何人、头像由嘉宾自助上传等关键行为。这些信息远超注解覆盖,且与注解无冲突。

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

该工具无输出 schema,描述完整覆盖调用前提(登录/主办方)、在业务链中的位置、参数默认值与限制、容量上限(30 位)、通知行为及头像处理方式。对于一个无输出 schema 的写入类工具,代理所需信息已足够完整。

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 描述覆盖率 100%,各参数含义已由 schema 提供。描述额外补充了‘每场最多 30 位’等约束,但对具体参数的语义说明基本重复 schema(如 confirmed 缺省值、userId 用途),未在参数层面提供实质性增量信息,符合 100% 覆盖率下的基线 3 分。

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?

明确说明具体动作:将某人录入活动嘉宾阵容,站内用户挂 userId,并指出这是邀请嘉宾的第一步。通过组合链和‘本工具不通知任何人’与 create_guest_invite_link、send_guest_invite_now 等兄弟工具区分开。

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?

给出完整的工具编排链:search_people 核对身份 → 本工具 → create_guest_invite_link → start_conversation/send_message 发送并确认。同时说明 confirmed 参数的使用条件,明确何时传 true。虽然未列出‘何时不用’,但链式上下文和替代步骤已经足够明确。

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.

Resources