spec: Add client features UX patterns (sampling/elicitation)#1011
Merged
olaservo merged 1 commit intomodelcontextprotocol:v2/mainfrom Feb 4, 2026
Merged
Conversation
Updates UX specs for better integration of client-initiated features: v2_ux_features.md: - Tools Screen: Inline client request queue during tool execution - History Screen: Hierarchical request trace showing parent-child relationships - Logging Screen: Request correlation with correlation IDs and chain filtering v2_ux_handlers.md: - Sampling Panel: Inline expansion pattern + tool calling flow (2025-11-25 spec) - Elicitation Handler: Inline expansion pattern with schema constraints - Sampling Providers & Testing Profiles: Extensible architecture for response handlers Key design decisions: - Request Trace Model shows causal chains between requests - Client requests appear inline with triggering tool calls - Auto-response profiles enable efficient testing workflows - Extensible provider architecture supports future LLM plugins 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates UX specs with patterns for client-initiated features (sampling, elicitation) that integrate into the request flow rather than appearing as disconnected modals.
Key Additions
Request Trace Model (History screen)
+45ms) for child requestsInline Client Request Queue (Tools screen)
Testing Profiles
Sampling Providers Architecture
Tool Calling Flow (per MCP 2025-11-25 spec)
toolsandtoolChoiceparameterstoolCallsfor multi-turn agentic loopsFiles Changed
v2_ux.md- Consolidated structure, inline wireframesv2_ux_features.md- Tools inline queue, History tree view, Logs correlationv2_ux_handlers.md- Sampling providers, testing profiles, inline expansion patternsRelated
v2/prototype/mantinebranch