Goono MCP

Prompts

The four procedural prompts the server provides

Prompts pin down the order in which tools are called. Summarizing and classifying is the client LLM's job; the server only fixes the sequence and the approval points. All four are always registered. Invoke them as slash commands such as /goono:summarize_notes (Claude Code) or from your client's prompt picker.

PromptPurposeArgumentsWrites
summarize_notesSummarize research notestarget, period?
review_reportReview reporttarget, status?
organize_homeTidy the project hometarget, hint?After you approve the plan
refactor_foldersRestructure folderstarget, goal?After approval: create → rename → move → delete

target is a project name or description. If several projects match, the LLM lists them and asks.

summarize_notes

Collects notes from the target project for period (for example "last week" or "2026-03") and summarizes them. The flow is list_projects → list_notes (date filter) → get_note_file for only the notes needed. The content bucket allows 60 calls per minute, so files are read sequentially and selectively.

review_report

Builds a report of review status for the target project. Narrow with status (for example REJECTED). Reviews are listed per project, so a project is required. Rejection reasons come from reviewers[].comment in get_review.

organize_home

Sorts notes sitting in the project home (outside any folder) into folders. Use hint to give a criterion such as "by experiment type".

  1. Stops if apiKey.scopes from get_me lacks write.
  2. Reads the home notes and existing folders, then presents a classification plan as a table.
  3. Calls create_folder and move_note only after you approve.

refactor_folders

Restructures the project's folders toward goal (for example "reorganize by year"). The execution order is fixed: create → rename → move notes → delete. A folder can only be deleted when empty (409 FOLDER_NOT_EMPTY), so notes are moved out first. As with organize_home, the write scope check and your approval come first.

On this page