Log work on a site
clickd_log_workRecords a step of work on a site: what you planned, changed or checked, or where you got stuck.
When: after each step, including one that carries out a proposal or a queued task.
Instead: clickd_propose before deploying to a site set to approve; clickd_todo for tasks waiting.
Inputs: site is a domain, like example.com. step is planned, changed, checked or stuck; did says what. found, files and rules (comma separated) add detail. proposal names the proposal carried out, task the queued task finished. Never send private data.
Returns: kept, site, step and note, with proposal or task and left when given.
Fails: a proposal or task not the person's keeps nothing and says so. Needs a person's key.
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": {
"site": "<site>",
"step": "<step>",
"did": "<did>"
},
"name": "clickd_log_work"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| did | Yes | What was done, in a sentence or two. | |
| site | Yes | The site, as a domain such as example.com. | |
| step | Yes | Which step this was. | |
| task | No | The queued task id this step finished. | |
| files | No | The files touched, separated by commas. | |
| found | No | What was true of the site, such as of its code. | |
| rules | No | The clickd rules worked on, by id, separated by commas. | |
| proposal | No | The proposal id, from clickd_propose, this step carried out. |