[CLI] MCP tool call summary omits nested object parameters (e.g. projectContext)

[bbarker]

When an MCP tool call is displayed in the TUI, the collapsed summary line only shows scalar/string parameters, omitting nested object parameters entirely. This makes it impossible to tell which project/target a tool is operating on.

Example:

The lib-install tool from the Unison MCP server takes both a projectContext (object with projectName and branchName) and scalar params (libProjectName, libBranchName). The TUI renders:

↓ lib-install
    ╰ libBranchName=main, libProjectName=@bbarker/uniclaw

But the actual call also includes:

{
  "projectContext": { "projectName": "Siaryey", "branchName": "main" },
  "libProjectName": "@bbarker/uniclaw",
  "libBranchName": "main"
}

The projectContext — which tells you which project is being modified — is completely invisible.

Expected behavior:

Nested object parameters should be represented in the summary, e.g.:

↓ lib-install
    ╰ projectContext.projectName=Siaryey, projectContext.branchName=main, libProjectName=@bbarker/uniclaw, libBranchName=main

Or at minimum, flatten one level with dot notation so the user can see what is being acted upon.

Environment:

• kiro-cli (latest as of 2026-05-08)
• macOS, aarch64
• MCP server: Unison (siaryey)

[github-actions]

Thanks for filing this detailed issue! The observation about nested object parameters being silently dropped from the MCP tool call summary is a great catch — having visibility into which project or context a tool is operating on is clearly important. A maintainer will take a look at this shortly. We appreciate you taking the time to include a clear example and suggested solution — that's super helpful! 🙌

[AnilMaktala]

We're doing a periodic backlog review and noticed this issue has been inactive for several months. Kiro has shipped a lot of changes since this was filed — we're now on IDE 1.0.309 and CLI 2.18.1 — and without any community uptake, we can't confidently prioritize it.

Closing to keep the backlog focused, but not as a dismissal. If you're still seeing this or others share the same experience, a new issue with your current version and any updated details would help us pick it back up. Issues with 👍 reactions from the community rise to the top fastest.