Manage an existing need (edit / close / status)
manage_needManage an existing need:
action='status': Get current state (active/closing/closed, remaining TTL, total matches, current safe_tags).
action='close': End the need. Closing erases the need's raw text + embedding immediately. But anything that already matched was already sent to the other party — closing can't pull that back (it stays in their match record, like an email you've already sent).
action='edit': For dating, For dating, confirm five facts with the user, then include these labels (English or Chinese), one per line or separated by semicolons: in i_offer: My age / 本人年龄 (18–99), Self-stated gender / 自述性别 (man, woman, nonbinary, other); in i_seek: Partner genders / 希望对方性别 (explicit genders or any), Partner age range / 希望对方年龄 (e.g. 22–28), Relationship intent / 关系目的 (long-term relationship, casual dating, friends first). Do not infer missing facts or resolve contradictory statements on the user's behalf. Change i_seek / i_offer / safe_tags. Changing content forces a re-extraction of safe_tags (unless you pass safe_tags explicitly) and re-runs matching against the active pool.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"need_id": "<need_id>",
"action": "<action>"
},
"name": "manage_need"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| i_seek | No | ||
| i_offer | No | ||
| need_id | Yes | ||
| safe_tags | No |