Skip to main content
Glama

独行录 / opcmenu

by io.github.yzlee
OverviewDiscussionsAdmin

批量算「还差哪几题」

get_signup_gaps
Read-onlyIdempotent

【需要登录】≤10场缺项按missingCombined合并，问一轮；默认取未报场次，显式slugs才含已报。get_signup_activity看题，update_my_signup_profile存通用项→submit_signup。普通附件用prepare_signup_file_upload，敏感附件去App。formUnknown须打开externalUrl；requiresAppActivation仅占位，须本人App确认，零缺项不代表能直接报。includeMyAnswers含本人联系方式勿转第三方；敏感项须现场重答。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo不传 slugs 时按关键词挑场（口径同 list_signup_feed：只匹配标题/主办方/城市/主办人昵称）
kindNo不传 slugs 时按类目取。取值：HACKATHON（黑客松） | COMPETITION（创业赛事） | INCUBATOR（孵化营） | FUNDING（融资申请） | COMMUNITY（社区入驻） | EVENT（活动报名） | OTHER（其他）
limitNo不传 slugs 时取几场，缺省 5，上限 10
slugsNo要盘的活动 slug 列表，最多 10 个；不传就取 list_signup_feed 前 limit 场里我还没报的
includeMyAnswersNo缺省 false。为 true 时每场多给「我已经有的答案（本人明文）+ 只能现场答的敏感题 + 需字节上传的附件题 + 外部表单地址」，用来给外链场导一份「这张表我该填什么」的清单

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / includeMyAnswers / description
      Previous value: -"缺省 false。为 true 时每场多给「我已经有的答案（本人明文）+ 只能现场答的敏感题 + 传不了的附件题 + 外部表单地址」，用来给外链场导一份「这张表我该填什么」的清单"New value: +"缺省 false。为 true 时每场多给「我已经有的答案（本人明文）+ 只能现场答的敏感题 + 需字节上传的附件题 + 外部表单地址」，用来给外链场导一份「这张表我该填什么」的清单"
  2. Changed2 schema fields changed
    • addedInput schema / properties / includeMyAnswers
      Added value: +{
+  "description": "缺省 false。为 true 时每场多给「我已经有的答案（本人明文）+ 只能现场答的敏感题 + 传不了的附件题 + 外部表单地址」，用来给外链场导一份「这张表我该填什么」的清单",
+  "type": "boolean"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "不传 slugs 时按关键词挑场（口径同 list_signup_feed：只匹配标题/主办方/城市/主办人昵称）",
+  "maxLength": 100,
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses a login requirement, the caveat that zero gaps does not mean the signup can be submitted, that sensitive items must be re-answered on site, and that includeMyAnswers carries the user's own contact details which must not be forwarded. These are meaningful behavioral caveats, though the dense jargon reduces immediate usability.

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?

The content is compact and front-loaded with the 【需要登录】 constraint, and each clause carries a distinct rule with no filler. However, it is a single dense run-on paragraph of shorthand with no structure, which hurts scannability.

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 complex signup-gap tool with no output schema, the description covers workflow integration, defaults, and edge cases (formUnknown, requiresAppActivation, sensitive answers, privacy of contact info). It hints at the missingCombined shape but does not fully describe the returned structure, leaving a small gap.

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?

With 100% schema coverage the baseline is 3, but the description adds real semantics beyond the schema: it states the default selection (unsigned activities unless explicit slugs, which then include already-signed-up ones) and the merge behavior tied to the ≤10 limit. It does not restate trivial field meanings.

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 (plus title) makes clear this computes the outstanding signup questions/gaps across up to 10 activities, merged per missingCombined. It is specific about the verb and resource and mentions sibling tools (get_signup_activity, submit_signup), though the core purpose is somewhat buried under procedural constraints rather than stated crisply up front.

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?

Explicit routing is provided: use get_signup_activity to view questions, update_my_signup_profile to store common items then submit_signup, prepare_signup_file_upload for normal attachments while sensitive attachments go to the App. It also states what to do for formUnknown (open externalUrl) and requiresAppActivation (confirm in App), covering when-to-use and when-not.

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