PicoClaw registers its tools dynamically at runtime. Each one can be enabled or disabled under tools in config.json; the tool switch table lists every tool with its switch, default state, and documentation.
| Family | Tools | Documentation |
|---|---|---|
| Filesystem | read_file, write_file, edit_file, append_file, list_dir, search_files |
Filesystem tools |
| Web | web_search, web_fetch |
Web tools |
| Command execution | exec |
Exec tool |
| Scheduling | cron |
Cron tool, Scheduled tasks and cron jobs |
| Messaging | message, reaction |
Messaging tools |
| Media | load_image, send_file, send_tts, image_generate |
Media tools, Image generation |
| Subagents | spawn, subagent, spawn_status, delegate |
Subagent tools |
| Skills registry | find_skills, install_skill |
Skills tools |
| MCP | mcp_<server>_<tool>, tool_search_tool_bm25, tool_search_tool_regex |
MCP tools |
| Hardware | i2c, spi, serial |
Hardware tools |
| Planning | todo |
Todo planning tool |
These apply to every tool and live in the same tools block:
allow_read_paths and allow_write_paths extend the workspace sandbox; protected credential files are always denied.filter_sensitive_data and filter_min_length redact secrets from tool results before they reach the model.max_inline_result_chars spills oversized tool output to a workspace artifact with a bounded inline preview.Tool visibility can be narrowed per agent and per request, on top of the global switches:
AGENT.md frontmatter tools: list restricts which registered tools an agent can see;turn_profile can further narrow exposed tools for specific requests (see Configuration).image_generate tool with OpenAI, Gemini, or OpenRouter models.