Skip to main content
Glama

独行录 / opcmenu

by io.github.yzlee
OverviewDiscussionsAdmin

发布需求

create_need

【需要登录】以当前用户身份发布一条需求（需求互换核心 loop 的起点）。先过后审：发布即展示在需求信息流，后台异步风控，不用等审核。发布后系统自动做向量撮合、推送给最匹配的主理人；也可以随后用 get_need_recommendations 主动看谁能满足。

【写好它】title 认真写清楚要什么（3–120 字）；detail 越具体，撮合和搜索越准。示例：「找人合作把我的效率工具做出海版本」「找能提供小程序代开发的主理人」。发布是公开动作：发布前把拟发的 title / detail 给用户过目确认。

【挂载】contextType+contextId 可把需求挂到自己的产品/活动/某人（成对传）。配图先用 upload_image_from_url 拿稳定 URL。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes需求类型：EXPERIENCE（寻找产品/作品） | QA（答疑求助） | RESOURCE（介绍资源） | COLLAB（寻求合作） | FINANCING（融资需求） | CHAT（找人聊聊找灵感） | GIG（兼职招募） | OTHER（其它）
titleYes需求标题，一句话说清要什么
detailNo详情：背景 / 具体要什么 / 什么样算合适，越具体越好
imagesNo配图 URL（先用 upload_image_from_url 镜像），最多 9 张
contextIdNo挂载对象 id，与 contextType 配对
contextTypeNo挂载对象类型，与 contextId 配对：product=自己的产品 / activity=活动 / user=某人 / goal=自己参与的合作目标（目标招募位，另有 create_goal_recruit_need 专用口）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / contextType / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "product",
-      "activity",
-      "user"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "product",
+      "activity",
+      "user",
+      "goal"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / contextType / description
      Previous value: -"挂载对象类型，与 contextId 配对"New value: +"挂载对象类型，与 contextId 配对：product=自己的产品 / activity=活动 / user=某人 / goal=自己参与的合作目标（目标招募位，另有 create_goal_recruit_need 专用口）"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses multiple important behaviors: the need is public, appears in the feed immediately ('先过后审'), passes through asynchronous risk control, and triggers automatic vector matching and push to suitable principals. It also warns that publishing is a public action and requires user confirmation before posting. This adds substantial context without contradicting the readOnlyHint=false and openWorldHint=true annotations.

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?

The description is organized into three labeled sections (【需要登录】【写好它】【挂载】), which makes it scannable and front-loads the most critical facts: authentication, immediate visibility, and public-action confirmation. Every sentence carries actionable content, and the examples are concrete and useful without padding.

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 six-parameter mutation tool with no output schema, the description covers all essential calling concerns: login requirement, side effects, moderation behavior, post-publish matching, content quality guidance, mounting semantics, and image preprocessing. The absence of a return-value description is a minor gap, but the overall operational picture is complete enough for an agent to select and invoke the tool correctly.

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?

Since schema coverage is 100%, the baseline is 3, but the description adds real value beyond the schema: it explains title quality expectations (3–120 characters), notes that detail specificity improves matching/search, clarifies that contextType and contextId must be passed as a pair, and instructs using upload_image_from_url for stable image URLs. This is meaningful guidance, though it does not add much for the type parameter beyond what the enum already provides.

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?

The description opens with '以当前用户身份发布一条需求' and positions it as '需求互换核心 loop 的起点', making the verb, resource, and scope explicit. It also differentiates from the sibling create_goal_recruit_need by noting the dedicated goal-recruitment entry, and references get_need_recommendations as a follow-up rather than a publishing action.

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?

The description clearly states when to use this tool (publishing a need for the current user) and gives explicit routing: for goal recruitment it points to create_goal_recruit_need ('另有 create_goal_recruit_need 专用口'), and for images it says to first use upload_image_from_url. It also suggests get_need_recommendations as the follow-up for seeing matches, providing sequencing and alternative selection.

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