MCP toolsWork and approvalsUpdated
Log what you did
What does mttr_log_work do?
Tells mttr what was done on a site after each step: what was planned, changed or checked, where it got stuck, and the files and rules involved. It shows on your progress page. A key may make this call on the sites it has claimed.
When to use it
- After each step of work on a site.
- When the work is stuck and you want it on record.
What you ask
You say“Log that you added sources to the drain guides.”
Your assistant calls
mttr_log_work({ site: "example.com", step: "planned", did: "did", found: "found", files: "files", rules: "rules", proposal: 10 })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
step | One of these | Yes | Which step this was.plannedchangedcheckedstuck |
did | Text | Yes | What was done, in a sentence or two. |
found | Text | No | What you found along the way, such as what was true of the site’s code. |
files | Text | No | The files touched, separated by commas. |
rules | Text | No | The mttr rules worked on, by id, separated by commas. |
proposal | Number | No | The proposal this step carried out or checked, by its id from mttr_propose, when the site works by approval. |
What comes back
- The entry, kept against the site.
- It shows on your progress page beside each read.
| When | Step | What was done |
|---|---|---|
| 10:42 | Changed | Added sources to 12 guides |
| 10:55 | Checked | Built the site, links resolve |
| 11:02 | Planned | Tap-to-call on service pages next |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is POST /api/v1/account/notes, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/account/notes" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"site":"example.com","step":"planned","did":"did","found":"found","files":"files","rules":"rules","proposal":10}'When it fails
| When | Status | What to do |
|---|---|---|
| Your assistant has no key yet | 401 over MCP | Sign up with mttr_signup, then connect again with the key it gives. |
Every error’s wording is in the API reference.
The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_log_work in the API reference.