claude-code - 💡(How to fix) Fix [FEATURE] Add intermediate view mode between default and verbose for MCP tool calls [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47970Fetched 2026-04-15 06:37:07
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Problem

The current view modes don't have a useful middle ground for MCP tool calls:

  • Default — Collapses MCP calls to just "Calling {server}..." which gives no visibility into what's actually being called
  • Verbose — Shows the full tool name, all parameters, and complete output, which floods the terminal when tools have large inputs (e.g. a 20-line SQL query)

Request

A "compact" view mode (or enhancement to default) that shows:

  • The full MCP tool name (e.g. mcp__forter__snowflake-query instead of "Calling forter...")
  • Truncated parameters (e.g. first 2-3 lines or N characters)

This would give enough context to understand what Claude is doing without dumping entire payloads into the transcript.

<img width="498" height="121" alt="Image" src="https://github.com/user-attachments/assets/bce51954-bc05-4ec4-9629-c1e1a10e7cd5" />

extent analysis

TL;DR

Implement a "compact" view mode that displays the full MCP tool name and truncated parameters to provide a middle ground between the default and verbose view modes.

Guidance

  • Identify the current implementation of the default and verbose view modes to understand how the MCP tool calls are being processed and displayed.
  • Determine the maximum number of characters or lines that can be displayed for truncated parameters without flooding the terminal.
  • Consider adding a configuration option to allow users to customize the level of detail displayed in the compact view mode.
  • Develop a truncation strategy for parameters, such as truncating at a specific character limit or displaying only the first few lines of output.

Example

# Example of how the compact view mode could be implemented
def format_mcp_tool_call(tool_name, parameters):
    truncated_parameters = "\n".join(parameters.split("\n")[:3])  # Truncate to first 3 lines
    return f"Calling {tool_name} with parameters: {truncated_parameters}"

Notes

The implementation of the compact view mode will depend on the specific requirements and constraints of the MCP tool and its users. The example provided is a simplified illustration of how the compact view mode could be implemented.

Recommendation

Apply workaround by implementing the compact view mode as described, as it provides a useful middle ground between the default and verbose view modes and addresses the user's request for more visibility into MCP tool calls.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING