all-tools — Claude Code command: what it does, how to install
Lists tools available in the current Claude Code session alongside TypeScript signatures and brief purpose descriptions. Useful when checking capabilities before starting a task.
npx claude-code-templates@latest --command utilities/all-toolsWhat all-tools does
The command parses active tools directly from the Claude Code system prompt. Instead of a freeform response, it returns a structured bulleted list where every tool displays its TypeScript function signature and return type.
Each entry includes a brief explanation of the tool's purpose. Points are separated by double line breaks. If a tool is not present in the current session prompt, the command will not detect it because it inspects only the active environment.
Originally created by IndyDevDan and DislerH, this template is distributed under the MIT license. You can install it using npx or by placing the markdown file inside .claude/commands/.
What it helps with
- inspect tools available in the current session
- verify TypeScript function signatures and parameter types
- select tools for an upcoming task
Example prompts for the agent
- /all-tools
- Show all available tools and parameters with /all-tools
- List every tool in the current session with its TypeScript signature
How to install all-tools
1claude-code-templates
npx claude-code-templates@latest --command utilities/all-tools2Manually: put the files in place
.claude/commands/all-tools.mdCall it with /all-tools. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/all-tools.mdCall it with /prompts:all-tools. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/all-tools.prompt.mdManually: put the files in place
.gemini/commands/all-tools.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about all-tools
How do I install all-tools in Claude Code?
Run npx claude-code-templates@latest --command utilities/all-tools. You can also manually save the command file to .claude/commands/all-tools.md.
What output format does all-tools use?
The command generates a bulleted list separated by double line breaks. Each entry contains a TypeScript function signature followed by a short explanation of the tool's purpose.
Where does all-tools get tool definitions from?
The prompt instructs the model to pull tool declarations directly from the system prompt of the active session.
Source text
all-tools.md · MIT
--- description: "Display all available development tools" --- # Display All Available Development Tools Display all available development tools *Command originally created by IndyDevDan (YouTube: https://www.youtube.com/@indydevdan) / DislerH (GitHub: https://github.com/disler)* ## Instructions Display all available tools from your system prompt in the following format: 1. **List each tool** with its TypeScript function signature 2. **Include the purpose** of each tool as a suffix 3. **Use double line breaks** between tools for readability 4. **Format as bullet points** for clear organization The output should help developers understand: - What tools are available in the current Claude Code session - The exact function signatures for reference - The primary purpose of each tool Example format: ```typescript • functionName(parameters: Type): ReturnType - Purpose of the tool • anotherFunction(params: ParamType): ResultType - What this tool does ``` This command is useful for: - Quick reference of available capabilities - Understanding tool signatures - Planning which tools to use for specific tasks
© davila7 · MIT · davila7/claude-code-templates
