Skip to main content
Glama

独行录 / opcmenu

by io.github.yzlee
OverviewDiscussionsAdmin

发布需求

create_need

【需要登录】发布真实公开需求，会触发异步匹配/推送；先确认title/detail，标题3~120字，写具体。contextType/contextId成对且须本人对象，图片先镜像。【组合链】create→get_need_recommendations→get_creator/contact_need；修改用update_need。

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.3/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world write. The description adds genuinely new behavioral context: it triggers async matching/push, requires login, requires images to be mirrored first, and constrains context objects to the caller's own. Useful beyond the annotations, though it does not describe reversibility (delete_need/cancel_need exist nearby but aren't referenced).

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?

Densely packed into bracketed clauses with the critical login requirement front-loaded. Every clause carries information, though the density and bracket notation make it slightly harder to scan than a plain-sentence version.

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 write tool with annotations and full schema coverage but no output schema, the description covers auth, side effects, param constraints, and the follow-up/alternative tools. Complete enough to call correctly; it just omits return-shape expectations and lifecycle (cancel/complete) context.

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 ownership semantics ('contextType/contextId 成对且须本人对象') and reinforces the 3–120 char title and image-mirroring requirement. This goes modestly beyond what the schema fields state.

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 real public need) and explicitly routes modification to the sibling update_need. An agent can distinguish create from update_need without opening either schema, and the schema further disambiguates create_goal_recruit_need.

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?

Gives explicit preconditions (login required, confirm title/detail first) and a follow-up chain (create→get_need_recommendations→get_creator/contact_need) plus the alternative for edits (update_need). Clear context, though it does not spell out when NOT to use this tool or contrast against create_goal_recruit_need.

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