recordClaudeDesktopJobCheck

Record the check of a Claude Desktop job

After Claude Desktop reported a job and you checked the changes yourself with your own tools, record the result: outcome "checked" when every change is in place, or "failed" when any is not, with a short summary. Only for a reported job, and only in the chat that prepared it. Tell the person what you checked as well.

Arguments

Argument	Type	Required	Description
`id`	string	required	The job id, for example J-0042.
`outcome`	enum (checked, failed)	required	"checked" when you saw every change in place yourself; "failed" when any change is missing or wrong.
`summary`	string	required	One or two plain sentences: what you checked and what you found.

Scopes

jobs:create

Annotations

Read only: no
Destructive: no

When to use

Use it in a chat in the Sasha web interface after Claude Desktop reported a job and you checked the changes yourself with your own tools. When Claude Desktop reports, Sasha starts a turn by itself in the chat that prepared the job, and that turn names the job. Read the report with checkClaudeDesktopJob, check each change, tell the person what you checked, then record the result.

id (required) is the job id, for example J-0001. outcome (required) is checked when you saw every change in place, or failed when any change is missing or wrong. summary (required, up to 2,000 characters) says in one or two plain sentences what you checked and what you found.

The job must be reported. A job's check is recorded once. After a failed check, offer the person a new job for the part that did not work. Only the person who approved the job can record its check, and only from the chat that prepared it. The tool needs jobs:create (admin and staff, in the chat in the Sasha web interface).

Example

{ "id": "J-0001", "outcome": "checked", "summary": "The welcome email is step 1 of the enquiry automation, and the automation is still off, as agreed." }

The structured result:

{ "id": "J-0001", "status": "checked", "checkSummary": "The welcome email is step 1 of the enquiry automation, and the automation is still off, as agreed." }

Refusals and what to do

A refusal is an error result. Its text is Error in recordClaudeDesktopJobCheck: <reason>.

Not found: no job of this person has this id. A job of another person gives the same answer. Check the id with checkClaudeDesktopJob.
job_not_reported: Claude Desktop has not reported this job, or Sasha has already recorded its check. …: call checkClaudeDesktopJob to see where the job is.
job_other_chat: this job belongs to another chat. …: record the check in the chat that prepared the job.
sasha_chat_only: …: the check is recorded only in a chat in the Sasha web interface.
If the connection does not hold jobs:create, the tool is not in your tool list, and a call to it returns MCP error -32602: Tool recordClaudeDesktopJobCheck not found.
Arguments that do not match the schema are refused before the tool runs, for example an outcome other than checked or failed.
internal:unexpected (request <id>): something failed inside Sasha. Quote the request id in suggestImprovement.

checkClaudeDesktopJob reads the report, and afterwards the summary of the check.
createClaudeDesktopJob prepares a new job, for example for a part that failed.
reportClaudeDesktopJob is how Claude Desktop sends the report that starts the check.