From ecccbb0b7fb609dd679d254746b03ae5e0a996ce Mon Sep 17 00:00:00 2001 From: olaservo Date: Sun, 7 Dec 2025 21:26:29 -0700 Subject: [PATCH] docs: add per-tool metadata feature to Tools Screen MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Address cliffhall's feedback about tool-specific metadata: - Add [Edit Metadata] button for per-tool _meta fields - Stored per-server, per-tool (not in global localStorage) - Merged with server-level metadata on each call 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- specification/v2_ux.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/specification/v2_ux.md b/specification/v2_ux.md index 5ef5d2c9..aeba441b 100644 --- a/specification/v2_ux.md +++ b/specification/v2_ux.md @@ -559,6 +559,10 @@ Each feature screen uses a **resizable panel layout** for flexibility. - Dropdown suggestions as user types - Supports enum and dynamic completion - Form generated from tool input schema +- **Per-Tool Metadata** - [Edit Metadata] button to set tool-specific `_meta` fields: + - Stored per-server, per-tool (not in global localStorage) + - Merged with server-level metadata on each call + - Use case: Different progressToken behavior, tool-specific tracking IDs - **Progress Indicator** from `notifications/progress`: - Progress bar with percentage - Step description if provided