{
  "capabilities": [
    "tool:file_manager"
  ]
}

{
  "ok": true,
  "equipped": [
    {
      "capability": "tool:file_manager",
      "instruction": "Manage text files and directories inside the active Zuza runtime workspace.\n\nCall tool id `file_manager` through the provider tool interface with arguments\nmatching this schema.\n\nValid call shape is always:\n{\n  \"operations\": [\n    {\"action\": \"read_file\", \"path\": \"example.txt\"}\n  ]\n}\n\nThe tool id is `file_manager`. Never call `file_manager.write_file`,\n`file_manager.read_file`, or any other dotted method name.\n\nDo not send `operation`, top-level `action`, or top-level `path`; put each file\noperation inside `operations`.\nDo not send shell command strings such as `command`; use `list_directory`,\n`read_file`, or another supported action.\n\nUse this tool instead of `python_console` for ordinary file operations.\n\nFor generated reports or other artifacts, write the content directly when it is\nready. Use `append_file` when the task naturally produces later sections or\nwhen updating an existing file; do not split solely to satisfy an arbitrary\ncharacter limit.\n\nSupported actions:\n- `create_directory`\n- `read_file`\n- `write_file`\n- `append_file`\n- `list_directory`\n- `exists`\n\nInput contract:\n{\n  \"operations\": [\n    {\"action\": \"create_directory\", \"path\": \"notes/research\"},\n    {\"action\": \"write_file\", \"path\": \"notes/research/summary.md\", \"content\": \"# Summary\", \"overwrite\": true},\n    {\"action\": \"append_file\", \"path\": \"notes/research/summary.md\", \"content\": \"\\n\\nMore notes.\"},\n    {\"action\": \"read_file\", \"path\": \"notes/research/summary.md\"},\n    {\"action\": \"list_directory\", \"path\": \"notes\", \"recursive\": true, \"max_entries\": 50},\n    {\"action\": \"exists\", \"path\": \"notes/research/summary.md\"}\n  ]\n}\n\nBehavior notes:\n- Paths are relative to the active runtime workspace. In a MiniZuza, this means\n  that MiniZuza's isolated workspace, not the Project Zuza application source.\n- Unqualified paths and `.` resolve inside the runtime-provided current chat\n  artifact folder. Use `.` to list that folder or search it recursively.\n- Explicit workspace-relative paths such as `artifacts/2026-07-23/chat_12/report.md`,\n  `uploads/source.pdf`, or `tools/example/main.py` may access other workspace\n  locations when the task requires it.\n- Reads and writes are UTF-8 text only.\n- The tool does not delete files or directories.\n- `write_file` creates parent directories when needed.\n- `append_file` creates the file if it does not exist.\n- General task deliverables default into the current chat artifact folder.\n- Every completed operation returns the canonical workspace-root-relative file\n  or directory address as `relative_path`. Copy that exact returned value for\n  later reads, edits, conversions, or `respond.attached_files`.\n- Use real source paths only when you are intentionally editing project files or\n  creating tools, senses, templates, tests, or project documentation.\n\nOutput contract:\n{\n  \"ok\": true,\n  \"tool\": \"file_manager\",\n  \"results\": []\n}"
    }
  ]
}