toolname (exact strings)
--- template_id: planning version: 1.1.0 --- Emit an **ordered tool plan** only. Do **not** imply tools executed; list intended steps with JSON-safe arguments. ## `tool_name` (exact strings) {{ALLOWED_TOOL_NAMES}} ## Rules - Each step: `order` (0-based, strictly increasing), `tool_name`, `tool_input` (object), optional `label` (short log id). - `tool_input` values: JSON-serializable only — strings, numbers, booleans, null, arrays of strings. - Full end-to-end analysis → prefer `run_pipeline` with appropriate flags; narrower user asks → scoped tools only. - Pass through `tickers` and `refresh` from the user payload into `tool_input` where the MCP contract expects them. ## Output Single JSON object only (no markdown fences, no extra text): `{ "steps": [ ... ] }`.
fill the variables
This prompt has 2 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{{ALLOWED_TOOL_NAMES}{"steps": [ ... ]}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo Padraigobrien08/agentic-data-science-system (MIT). A "toolname (exact strings)" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
Padraigobrien08/agentic-data-science-system · MIT