Skip to main content
Glama

读 / 改群公告

feishu_chat_announcement

Read or update a Feishu group's top announcement: fetch current content, replace it entirely, or append new text. Requires the bot to be group owner or admin for changes.

Instructions

群公告是群顶部那条所有人都能看到的说明。action=get 读现有内容;action=set 改写(mode=replace 整段替换,mode=append 接在末尾)。改公告需要机器人是群主或管理员。

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

Input Schema

NameRequiredDescriptionDefault
modeNoaction=set 时用:replace 整段替换(默认),append 接在末尾。
actionYesget 读、set 写。
chat_idYes群 id(oc_ 开头)。
contentNoaction=set 必填,新公告正文(支持纯文本与换行)。

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 only declare readOnlyHint=false and openWorldHint=true; the description adds two meaningful facts beyond them: the permission requirement (owner/admin) and the social visibility of the announcement (everyone in the group can see it), which signals that writes are public. However it does not disclose what happens on get when no announcement exists, or whether replace can be undone.

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?

Three tight sentences: resource definition first, action semantics second, permission constraint last. Every sentence earns its place. The opening definition of the announcement is helpful context rather than padding.

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 four-parameter, no-output-schema tool, the definition covers the resource, both actions, the mode variants, and the authorization requirement. The remaining gaps, empty-state behavior and error responses, are minor for a tool whose parameters are fully self-documented.

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%, so every parameter is already documented, including enums, defaults, and the action=set requirement for content. The description restates the action and mode semantics without adding syntax or format meaning beyond the schema. Baseline 3 is appropriate when the schema carries the load.

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?

The description names a specific resource (the group announcement shown at the top of the chat) and explains both verbs it supports, action=get reads and action=set rewrites. This makes the dual-mode nature unambiguous. It stops short of naming a sibling it differs from, but the resource is unique enough to be identifiable.

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?

It gives explicit context for choosing each action: get for reading existing content, set for rewriting, with replace vs append explained. It also states a hard prerequisite, that the bot must be group owner or admin to modify. There are no explicit when-not-to-use caveats, so it falls short of a 5.

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