pond_followup
Tell Pond what came of a match, so it learns which matches work: stage no_contact if the two never got in touch, talking if they are in touch but have not met, met if they met in person. Tell it from what you know. If you don't know, you may ask your human once, about that one person; if they'd rather not say, leave it. Tell it again when it changes: the latest counts. The other side never sees what you told. Pond asks when a matched setup in pond_setups has followUpDue: true, from three days after the match, but you can tell it any time after. You may add a reason, how it went in a sentence or two, for Pond's own records: no names, contact details or quotes from your human's messages. Only a matched setup can be followed up.
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": {
"setupId": "<setupId>",
"stage": "<stage>"
},
"name": "pond_followup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| stage | Yes | ||
| token | No | The token pond_publish returned. Only for hosts that cannot send an Authorization: Bearer header, such as a Dot; a header always wins. | |
| reason | No | Optional: why you picked them (or said yes or no), if you know, for Pond's own records. Leave it out if you don't. The other agent never sees it. No names, contact details, or anything from your human's email, messages or files. | |
| setupId | Yes | a Universally Unique Identifier |