Skip to main content
Glama

改群信息(群名 / 描述 / 谁能拉人)

feishu_chat_update

Updates Feishu group chat details and permissions—name, description, who can invite members, share group cards, or @all—by sending only changed fields; other settings remain unchanged.

Instructions

改群名、群描述,或调整「谁能邀请成员 / 谁能分享群名片 / 谁能 @所有人」。只传要改的字段,其它保持不动。

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": {
      "chat_id": "<chat_id>"
    },
    "name": "feishu_chat_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo新群名。
chat_idYes群 id(oc_ 开头)。
descriptionNo新群描述。
at_all_permissionNo谁能 @所有人。
add_member_permissionNo谁能拉人进群。
share_card_permissionNo群成员能否分享群名片。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the mutation and external-effect profile is already known. The description adds genuine behavioral value by disclosing partial-update semantics (omitted fields are left untouched), but says nothing about authorization requirements, whether permission tightening affects existing members, or whether the change is reversible.

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?

Two sentences, no filler, with the editable surface enumerated first and the key operational rule (partial update) placed second. Every clause earns its place.

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 6-parameter tool with full schema documentation and no output schema, the description covers all editable fields plus the update semantics that an agent most needs. The remaining gap is permission/auth context, which matters for a permission-changing mutation but is not covered here or in annotations.

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% and all three enum parameters carry their allowed values in the schema, so the schema already carries the semantics. The description only restates the field groups and adds the partial-update rule; it adds no format, constraint, or edge-case detail beyond the schema.

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 (改) plus the exact resource and the four editable attribute groups (群名, 群描述, 邀请/名片/@所有人权限), so an agent can tell this is a settings-mutation tool rather than a create/dissolve/announcement tool. It stops short of naming any sibling to contrast with, so differentiation relies on the reader's knowledge of feishu_chat_create / feishu_chat_announcement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"只传要改的字段,其它保持不动" is a real invocation rule that prevents the common mistake of resending the full object. However, there is no explicit when-to-use versus when-not guidance and no mention of prerequisites such as needing owner/admin rights, which is the main ambiguity for a permission-changing tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.