Raw tool output floods your context window. Use context-mode MCP tools to keep raw data in the sandbox.
- GATHER:
batch_execute(commands, queries)— Primary tool for research. Runs all commands, auto-indexes, and searches. ONE call replaces many individual steps. - FOLLOW-UP:
search(queries: ["q1", "q2", ...])— Use for all follow-up questions. ONE call, many queries. - PROCESSING:
execute(language, code)orexecute_file(path, language, code)— Use for API calls, log analysis, and data processing. - WEB:
fetch_and_index(url)thensearch(queries)— Fetch, index, then query. Never dump raw HTML.
- DO NOT use Bash for commands producing >20 lines of output — use
executeorbatch_execute. - DO NOT use Read for analysis — use
execute_file. Read IS correct for files you intend to Edit. - DO NOT use WebFetch — use
fetch_and_indexinstead. - DO NOT use curl/wget in Bash — use
executeorfetch_and_index. - Bash is ONLY for git, mkdir, rm, mv, navigation, and short commands.
- Keep responses under 500 words.
- Write artifacts (code, configs) to FILES — never return them as inline text.
- Return only: file path + 1-line description.