guide
Read AATAM's guide. AATAM's way of talking, coaching method and links, read by need, read only: strengths (no idea yet), coaching (something feels hard), moment, pattern or card (with id), links, voice. Guidance for you, never for ordinary work; say it in your own words.
Where it is
In the office area (search, the AI call log, her settings, and opening parts of her office): open it with tools_for { area: "office" }, then call it with read_tool { name: "guide", args }.
Does it need a yes?
Reads only: it changes nothing. Here: AATAM's voice, method and links: product guidance, nothing of hers.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
need | "strengths" | "voice" | "coaching" | "moment" | "pattern" | "card" | "links" | "examples" | yes | |
id | string | no | moment, pattern or card: which one. · 1 to 100 characters |
run_id | string | no | The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters |
Example
{
"name": "guide",
"arguments": {
"need": "strengths"
}
}When it is refused
invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.taken: Someone else holds it (another AI on that task). Pick another task.stale: It changed since you read it. Read it again and use the new version.failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.