complete_need
shallowio.github.yzlee/opcmenu · Verify this server
【需要登录】在某个接洽会话里点「完成需求」。**双方各确认一次**：发起人和承接人都要在同一会话里各调一次本工具，双方都确认后该承接才置 COMPLETED；只有一方调过时处于等待对方确认状态（看返回的 authorDoneAt / claimerDoneAt）。 【前置】conversationId 必须是 contact_need 建立的那个会话。确认是真实状态变更，调用前先向用户确认「事情确实办完了」。 【失败语义】非该需求当事人 403 not_party_to_need；会话没绑这条需求 409 no_claim_for_conversation；已完成 409 need_already_completed；已取消 409 need_closed。
1 trials · measured 27 days ago
complete_need scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.yzlee/opcmenu, measured 11 Sept 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-09-11 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/ed8f31a0-fcf5-4f51-98ef-dd6d9d8e1c9b)