Skip to main content
Glama
Sign In

独行录 / opcmenu

by io.github.yzlee
OverviewDiscussionsAdmin

更新我的多角色画像

set_my_role_profile
Idempotent

登录;确认后写融资/投资人/机构等角色信息，逐字段合并，未传保留；空串清字段，清整树先确认。venture.productStage与completedRound独立，null撤销对应自报；旧stage不能混传。completedRound仅已完成融资，none未融资/unknown未知；目标轮次用fundraising.round。Pre-A→天使，A+→A，E/Pre-IPO/上市→D及以后；融资不证明上线/收入/盈利。公开自由文本受content_rejected闸；短信验证的主办资料只能App改。回执核对→get_my_positioning；融资→list_funding→get_creator。

Input Schema

NameRequiredDescriptionDefault
orgNo机构身份。type 必须有（新建时必给）：park（园区） | competition（赛事主办） | service（企业服务）；resources 是**字符串数组**（工位/注册地址/政策补贴/算力…），不是一段话
seekerNo来找主理人的那批人：kind = media（媒体） | recruiter（招人） | buyer（采购） | partner（找合作） | other（其它）；lookingFor 想找什么、purpose 办成什么事、org 所属机构名（≠自有公司）、timeline 什么时候要
ventureNo产品阶段与已完成融资轮次，可以同时设置；不传的维度保持原值；stage仅用于旧调用兼容
aspiringNo在校/待入行：education 一句话经历、weeklyHours 每周可投入、gigWilling 愿不愿先接活
investorNo投资人身份。type 必须有（新建时必给）：individual（个人投资人） | corporate（产业投资） | institution（投资机构）；rounds/sectors 是字符串数组
fundraisingNo融资情况。active=是否在融资（新建这棵子树时必须给）；round/amount/requirements 都是自由文本；bpUrl 是已上传的 BP 文件地址
needsOfficeNo主理人：需要办公/注册地址
needsGigHelpNo主理人：需要兼职帮手

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / venture / description
      Previous value: -"创业阶段（同时就是定位栏台阶上的阶段：主线五级 + 融资阶段，走专门的写入口）"New value: +"产品阶段与已完成融资轮次，可以同时设置；不传的维度保持原值；stage仅用于旧调用兼容"
    • addedInput schema / properties / venture / properties / completedRound
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "unknown",
+        "none",
+        "seed",
+        "angel",
+        "series_a",
+        "series_b",
+        "series_c",
+        "series_d_plus"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "最近一次已完成融资轮；none=明确未融资，unknown=资料不足，null=交由系统判断。不是正在融的目标轮次"
+}
    • addedInput schema / properties / venture / properties / productStage
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "idea",
+        "build",
+        "launch",
+        "revenue",
+        "profit"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "产品与经营阶段，与融资独立；null仅撤销该维度自报，交由系统判断"
+}
    • changedInput schema / properties / venture / properties / stage / description
      Previous value: -"创业阶段自报值；传 null = 撤销自报，交回系统判。seed 及以后 = 最近一次已完成的融资轮；正在融的轮次写 fundraising.round。取值：idea（找想法） | build（开发产品） | launch（产品上线） | revenue（有收入） | profit（有盈利） | seed（种子轮） | angel（天使轮） | series_a（A轮） | series_b（B轮） | series_c（C轮） | series_d_plus（D轮及以后）"New value: +"旧单阶段兼容入口，请优先用productStage/completedRound；不能与新字段混传。取值：idea（找想法） | build（开发产品） | launch（产品上线） | revenue（有收入） | profit（有盈利） | seed（种子轮） | angel（天使轮） | series_a（A轮） | series_b（B轮） | series_c（C轮） | series_d_plus（D轮及以后）"
    • removedInput schema / properties / venture / required
      Removed value: -[
-  "stage"
-]
  2. Changed3 schema fields changed
    • changedInput schema / properties / venture / description
      Previous value: -"创业阶段（同时就是定位栏主线阶段，走专门的写入口）"New value: +"创业阶段（同时就是定位栏台阶上的阶段：主线五级 + 融资阶段，走专门的写入口）"
    • changedInput schema / properties / venture / properties / stage / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "idea",
-      "build",
-      "launch",
-      "revenue",
-      "profit"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "idea",
+      "build",
+      "launch",
+      "revenue",
+      "profit",
+      "seed",
+      "angel",
+      "series_a",
+      "series_b",
+      "series_c",
+      "series_d_plus"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / venture / properties / stage / description
      Previous value: -"创业阶段自报值；传 null = 撤销自报，交回系统判。取值：idea（找想法） | build（开发产品） | launch（产品上线） | revenue（有收入） | profit（有盈利）"New value: +"创业阶段自报值；传 null = 撤销自报，交回系统判。seed 及以后 = 最近一次已完成的融资轮；正在融的轮次写 fundraising.round。取值：idea（找想法） | build（开发产品） | launch（产品上线） | revenue（有收入） | profit（有盈利） | seed（种子轮） | angel（天使轮） | series_a（A轮） | series_b（B轮） | series_c（C轮） | series_d_plus（D轮及以后）"
  3. First observed

TDQS

A3.9/5.0
Behavior5/5

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

The annotations declare idempotency and non-destructiveness, while the description adds substantial behavior beyond that: field-by-field merging, omitted fields retained, empty strings clearing fields, null revoking self-reported dimensions, confirmation before clearing an entire tree, content rejection gates, and App-only restrictions. The field-clearing behavior is mitigated by the stated confirmation requirement, so it does not clearly contradict destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact in raw length, but it is a single dense semicolon-separated run-on mixing authentication, mutation semantics, enum rules, restrictions, and follow-up calls. Most clauses earn their place, but symbols like '→' and the lack of structure make it harder to scan and parse.

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 nested eight-parameter mutation tool with no output schema, the description covers the key write semantics, merge behavior, constraints, and follow-up tools such as get_my_positioning, list_funding, and get_creator. It still does not describe the response or receipt shape itself, relying instead on follow-up calls, so it is not fully complete.

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 description coverage is 100%, so the schema already carries the baseline parameter meaning. The description still adds important cross-field semantics: venture.productStage and completedRound are independent, null revokes the corresponding self-report, old stage cannot be mixed, target round uses fundraising.round, and completedRound only represents completed financing. It does not add meaning for every top-level field, but the added constraints are significant.

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 states a concrete verb ('写' write) and resource (融资/投资人/机构 role information), and it explains the merge-and-retain behavior. It does not explicitly name a sibling such as update_my_profile to differentiate itself, and the leading '登录' adds auth context rather than purpose, so it falls short of a 5.

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?

It gives some conditional guidance: old stage cannot be mixed with new fields, target round should use fundraising.round, and SMS-verified organizer materials can only be changed in the App. However, it never clearly states when to choose this tool over update_my_profile, set_persona, or other profile-related siblings, so selection guidance is mostly implied.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources