MCP Tool Log Display Creates Unreadable Two-Column Layout on Narrow Terminals

Problem

The MCP tool log display in Claude Code uses the tool name length for indentation, causing severe readability issues when:

• Tool names are long (e.g., mcp__google-sheets__write_spreadsheet)
• Terminal width is narrow
• The combination creates a cramped two-column layout

Current Behavior

When displaying MCP tool calls, the entire parameter JSON gets formatted in a narrow right column, making it nearly impossible to read the actual tool parameters.

Visual Example

● google-sheets - write_spreadsheet (MCP)(s
                                        pr
                                        ea
                                        ds
                                        he
                                        et
                                        Id
                                        :
                                        "1
                                        TN
                                        P5
                                        et
                                        9_
                                        NX
                                        ...

Expected Behavior

Tool logs should use consistent, reasonable indentation that doesn't depend on tool name length. Options:

1. Fixed indentation: Use a consistent 2-4 space indent regardless of tool name length
2. Wrap after tool name: Put parameters on new lines with standard indentation
3. Responsive formatting: Detect terminal width and adjust accordingly

Suggested Format

● google-sheets - write_spreadsheet (MCP)
  spreadsheetId: "1TNP5et9_NXGi3GV8L61IxUcV7ZlnNOU2e1Gz15RYzzo"
  range: "Sheet1\!A1:B2"
  values: [["Name", "Value"], ["Test", "123"]]

Environment

• Terminal width: varies (issue more pronounced on narrow terminals)
• Affects all MCP tools with long names
• Impacts readability of tool parameters and debugging

Impact

• Makes debugging MCP tool calls extremely difficult
• Poor user experience when reviewing tool execution
• Particularly problematic for MCP tools with verbose parameter names