Skip to content

fix(client): keep field descriptions visible#1468

Open
go165 wants to merge 1 commit into
modelcontextprotocol:mainfrom
go165:go165/filled-field-descriptions
Open

fix(client): keep field descriptions visible#1468
go165 wants to merge 1 commit into
modelcontextprotocol:mainfrom
go165:go165/filled-field-descriptions

Conversation

@go165

@go165 go165 commented Jun 14, 2026

Copy link
Copy Markdown

Fixes #1401.

Summary

  • Render schema field descriptions as persistent helper text for scalar tool inputs instead of only relying on placeholders.
  • Apply the same behavior in the Apps tab input form.
  • Add regression coverage for descriptions remaining visible after users fill the field.

Testing

  • npm test -- --runTestsByPath client/src/components/__tests__/ToolsTab.test.tsx client/src/components/__tests__/AppsTab.test.tsx --runInBand

This is a source-only frontend PR; no deployment was performed.

@shapkarin shapkarin left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for this PR!

@@ -519,6 +533,11 @@ const AppsTab = ({
<Textarea
id={key}
placeholder={prop.description}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite sure we need still need a description as a placeholder. After this PR, the description is shown below and empty areas display it twice.

Image

@@ -564,6 +583,11 @@ const AppsTab = ({
type="number"
id={key}
placeholder={prop.description}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the same for input placeholders

Image

return (
<p
id={id}
className="mt-1 text-xs text-muted-foreground whitespace-pre-wrap"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could use the same text size as the placeholder so the text is easier to see.

Suggested change
className="mt-1 text-xs text-muted-foreground whitespace-pre-wrap"
className="mt-1 text-sm text-muted-foreground whitespace-pre-wrap"

@shapkarin

Copy link
Copy Markdown

@go165 don’t get me wrong, no any condemnation at all. After reviewing it, I created a PR to your fork and branch, go165#1, so if everyone is okay with it, after merger go165#1 it could become part of your upstream PR. Pure collaboration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[enhancement] Keep MCP tool property descriptions visible for filled inputs

2 participants