Skip to main content
Glama

独行录 / opcmenu

by io.github.yzlee
OverviewDiscussionsAdmin

发消息圈

publish_moment

【需要登录】以本人名义公开发消息圈，进入关注者/同组织/匹配者信息流及撮合；只能删不能改，正文仅本人说过的话，发前念给用户确认。文字+最多9图+可选活动/产品/需求/组织卡片。本人发来的图放 images；外图先 upload_image_from_url(kind=moment-image)，其它实体图请挂卡，id 从 list_my_activities/get_my_products/list_my_needs/list_my_organization_memberships 获取。visibility 默认公开；仅组织内可见须 visibility=organization+organizationId。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNo图片地址，最多 9 张，按顺序展示
contentNo正文（纯文本，最多 2000 字）
attachIdNo挂卡对象 id（活动也可传 slug）；与 attachType 成对
attachTypeNo挂卡类型：activity 活动 | product 产品 | need 需求 | organization 组织；与 attachId 成对
visibilityNopublic 公开（缺省，所有登录用户）| friends 仅互相关注的好友 | private 仅自己 | organization 仅某组织成员（须同时给 organizationId）
aiDeclarationNo用户声明AI才true；省略不证人工；agent非依据。
organizationIdNo只在 visibility=organization 时给：发在哪个组织（用户须是在册成员；id 从 list_my_organization_memberships 拿）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / aiDeclaration
      Added value: +{
+  "description": "用户声明AI才true；省略不证人工；agent非依据。",
+  "type": "boolean"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / organizationId
      Added value: +{
+  "description": "只在 visibility=organization 时给：发在哪个组织（用户须是在册成员；id 从 list_my_organization_memberships 拿）",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / visibility / description
      Previous value: -"public 公开（缺省，所有登录用户）| friends 仅互相关注的好友 | private 仅自己"New value: +"public 公开（缺省，所有登录用户）| friends 仅互相关注的好友 | private 仅自己 | organization 仅某组织成员（须同时给 organizationId）"
    • changedInput schema / properties / visibility / enum
      Previous value: -[
-  "public",
-  "friends",
-  "private"
-]New value: +[
+  "public",
+  "friends",
+  "private",
+  "organization"
+]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only carry the generic mutation profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true). The description adds real behavioral context beyond that: login is required, posts are public and feed into other users' streams, they can only be deleted and never edited, and content must be the user's own words read back for confirmation.

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?

Dense but well front-loaded: login requirement and core action lead, workflow details follow. Nearly every clause carries operational information, though the long final sentence packing image/card/visibility rules is a bit heavy.

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?

For a 7-param write tool with no output schema, the description covers auth, edit/delete semantics, feed reach, image-vs-card handling, id sources, and visibility conditions. Nothing essential for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-field and cross-tool meaning: it explains the images source workflow, the attachType/attachId pairing with the exact id-lookup tools, and the visibility=organization + organizationId coupling. It does not add new syntax for content or aiDeclaration, so it stops short of 5.

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?

States a specific verb+resource (publish a moment in your own name) and goes further by describing the downstream effect (enters follower/org/matcher feeds and matching). It is readily distinguishable from siblings like delete_my_moment, get_moment, and list_moments_feed.

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?

Gives concrete when-to/how-to guidance: user-provided images go in images, external images must first go through upload_image_from_url(kind=moment-image), other entity images should be attached as cards with ids sourced from specific list_* tools, and visibility defaults to public while org-only view requires visibility=organization plus organizationId. It also states the pre-post confirmation requirement, leaving little to inference.

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

All 独行录 / opcmenu toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources