For agents

The EVY tools

EVY’s tools come from one MCP server, named evy. A folder agent gets all of them. A chat in Claude.ai or ChatGPT gets a smaller set, without folders, plus one of its own: whoami, which names the person signed in. When EVY’s plugin is installed, the tools may show up twice: use the plugin’s copy, which knows the folder you work in, and leave the other alone.

Each tool is named exactly as the server names it. The sections below follow the order you meet them: reading the space, working a task, writing to the space, the notes, and the rest.

get_context

The space the folder you work in belongs to: its briefing, initiatives, open tasks, the person’s standing instruction, what was decided this week and where the space stands.

Use it when your session did not start with the space’s context, or when you need the whole picture before you plan.

list_spaces

The person’s spaces, one per company or area of life, each with its open initiatives, Regular tasks and folders.

Use it when you need to know which spaces exist, or which folder belongs to which space.

list_tasks

The person’s tasks in any space, newest plans first, filtered by space, words or handle, day, status, who does it, or when it was made or changed.

Use it to find work you were not given by id, or to see what else is planned in a space.

get_task

One task in full: its prompt, notes, checklist and result, the last report, the thread, and the parts of a split task.

Use it before you claim a task, and whenever the person asks about one.

claim_task

Takes a task before you work on it, so no other session takes it too, and turns it to running.

Use it as the first thing you do on any task. Pass session and the folder you are in. The answer’s start part names the folder to work in and the rules to follow.

report

Delivers a task, with the result written for someone who saw none of the earlier rounds, and a status of done or blocked.

Use it to finish. It replaces anything reported before, so write the whole result each time.

ask

Puts one question to the person on a task you run, with the options and your recommendation, then stops.

Use it when only the person can answer. When the answer is a choice, send 2 or 3 options and mark the one you recommend.

comment

A short progress note in a task’s thread, which the person sees in EVY.

Use it for a step worth telling them about, and to pass a checklist when your harness has no hooks. In a space shared with teammates, it is also how you help on a teammate’s task: agents change only their own person’s tasks, and never copy their person’s Private notes into a shared task without asking.

update_task

Changes a task in the space of your folder: its notes, checklist, links, day, who does it, and its state.

Use it to keep a task honest while you work, and to hand it on.

add_task

A new task in the space of your folder, for today unless scheduled_date says otherwise.

Use it only when the person asked for a task, or asked you to hand work off. A task for an agent carries a prompt a fresh session can run from and a done_when.

add_plan

Saves a plan with steps for later sessions or for the person: one task per step, chained so a step starts only once the one it waits on is done, all in one initiative, plus a Plan document the space’s Plans list draws from.

Use it when you name later sessions in a concept, a plan or your result, before you report.

An initiative has one plan. Saved into an initiative that already has one, the steps join it as its next round, with title and why naming the round, and after may name a step of an earlier round. Save the concept the round comes from as a note first with save_note, then name it in decided_in (the note’s id, or the path of its file in the space’s folder): the Plan document links it in the round and in Sources. A new goal gets a new initiative instead of a round. The Plan document shows the rounds in order, a finished one folded to one line.

split_task

Splits the task you are running into one to five parts that run one after another, each with a prompt and a done_when.

Use it when the work is more than one session does well and falls into steps that each end in something concrete the next one reads. Keep one tight piece of thinking whole.

propose

Suggests work you found but should not just do. The person decides later, without your session.

Use it for work outside your task that moves a goal or unblocks something. Each title and summary says the outcome in everyday words, and reason ties it to a goal or a date.

record_decision

Records something the person decided while working with you: what was decided and why, in at most 40 words.

Use it as soon as they decide. It goes into the space at once, marked as recorded by you.

update_progress

Replaces the space’s progress summary: where it stands, what changed lately and what comes next, in at most 150 words.

Use it when your work changes where the space stands. Start from the summary get_context gives you and change only what changed.

The person’s notes in EVY found by words and meaning, best first: their private notes and their spaces’ shared ones, or one space’s.

Use it to find what the space already knows before you write or decide anything.

knowledge_page

One of the person’s notes in EVY in full, as Markdown, by the id knowledge_search gave. With as_of, as it read at the end of that day.

Use it when a search snippet is not enough. Each fact line ends with its source and date: write them beside any fact you use.

save_note

Saves Markdown into the person’s notes in EVY: a new note that waits in their Review of the space, or an addition at the end of a note they can read. It answers with the note’s link, and for an agent on the person’s computer also a link that opens the note in EVY Desktop.

Use it for anything the person will reuse, edit or share: a pitch, a draft to send, a plan for themselves, research they will come back to, a checklist. With EVY’s plugin the note goes into the space of the folder you work in; a chat names the space. End your reply with the line it answers with, as it is: the note’s title linked to the note in EVY, then “Open in EVY Desktop” when you work on the person’s computer. The first link opens wherever the reply is read; the second opens the note inside EVY Desktop on a Mac that has it. add_plan answers with the same links for its Plan document. Code and developer docs stay in the repository, and a write-up the person only reads once stays on the task’s result.

suggest_edits

Leaves changes in one of the person’s EVY notes as suggestions they accept or reject one by one or all at once.

Use it when the person asks you to edit, check, proofread or improve a note. Read the note with knowledge_page first. Nothing changes until they accept.

note_threads

Lists the comment threads on a note: the passage each hangs on, who wrote, and what was said.

Use it before you answer a comment. Read the open threads first.

reply_in_note_thread

Replies in a note’s comment thread as the agent. The people in the thread hear about it.

Use it to answer what was asked in a thread, in plain sentences.

comment_on_note

Starts a comment thread on a passage of a note, as the agent. Quote the passage’s words exactly.

Use it to raise something about one passage, rather than about the note as a whole.

resolve_note_thread

Settles a note’s comment thread once it is answered or needs nothing more. It stays readable.

Use it after you reply, so the thread stops waiting on anyone.

bring_email_tasks

Hands EVY the emails in the person’s inbox that need something from them, found with your own Gmail access. EVY has none of its own. Each email becomes a suggestion only the person sees, and a draft reply you wrote waits in their Review with Open in Gmail.

Use it for the daily inbox sweep, once per sweep, and with an empty list when nothing needs the person. Write each title, summary and brief in your own words: if the person takes the task into a shared group, the team reads those, never the email.

save_to_library

Saves a web page, or the part of it the person chose, to their Library in EVY.

Use it when the person says “save this”, “remember this” or “keep this” about a page. Pass the url, the part they picked, and anything they said about it as note.

make_image

Makes one image from your prompt, using the person’s own image key, and gives you the command that saves it.

Use it when the task needs a picture. Write the prompt yourself from the brief: subject, style, light, composition and any text the image must show. Name the file with an OUTPUT: line in the report.

add_lesson

Adds what you learned to the working rules note of the folder you work in, so every agent that works there later reads it in its task prompt.

Use it for a trap, a command that works or fails, or a rule you had to find out the hard way: one or two plain sentences, with the reason. Not for the task’s own progress.

Adds a folder to the folders a space uses, once the person said which space it belongs to. EVY reads it once and watches it after.

Use it when you work in a folder that belongs to no space, after the person names the space.

hand_to_mac

Moves a task running on the person’s EVY box to their Mac agent, with your note at the top of its brief.

Use it only when a step needs the Mac: files outside the space’s folders, a Mac app, a website they are signed into in their own browser, or a machine only the Mac reaches. Do everything you can on the box first, commit and push, then call it and stop. Never use it to skip work the box can do.