MCP tool calls: show first argument for all tools, not just path-based ones

Resolved 💬 3 comments Opened Feb 22, 2026 by TristanSpeakEasy Closed Mar 23, 2026

Description

When Claude Code displays MCP tool calls in the output, it shows the first argument value next to file-based tools but not for other tools like execute_command.

Current behavior:

  • my-server [apply_diff] package.json — shows the path argument ✓
  • my-server [write_file] src/index.ts — shows the path argument ✓
  • my-server [execute_command] — no argument shown ✗

Expected behavior:

  • my-server [execute_command] npm run build — should show the command argument

It seems like Claude Code only extracts and displays arguments named path (or similar) next to the tool name. It would be helpful if it showed the first (or most relevant) string argument for all MCP tools, so users can quickly see what command is being run without expanding the tool call.

This is especially useful for terminal/command execution tools since the command string is the most important context for the user when reviewing tool calls.

Environment

  • Claude Code CLI
  • MCP server providing tools with various parameter shapes

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗