@crypto512/jicon-mcp 2.2.1 → 2.3.19

package/TOOL_LIST.md

@@ -5,19 +5,20 @@ This document provides a comprehensive reference of all available tools in the J
 
 ## Summary
 
-**Total Tools**: 79
-- **Jira Tools**: 26 (21 read + 5 write)
-- **Confluence Tools**: 21 (13 read + 8 write)
-- **Tempo Tools**: 13 (10 read + 3 write)
-- **Buffer Tools**: 11
-- **Workload Tools**: 2
-- **URL Tools**: 2
-- **Jicon Help Tools**: 1
-- **Date Tools**: 1
-- **PlantUML Tools**: 3
+**Tool Categories**:
+- **Jira Tools** - Issue search, CRUD, transitions, comments, boards, sprints, epic analysis
+- **Confluence Tools** - Page search, CRUD, draft workflow, review workflow, comments, attachments
+- **Tempo Tools** - Worklog management, accounts, teams, time analysis
+- **Buffer Tools** - Content buffering, XHTML editing, transformation, schema discovery
+- **Workload Tools** - Time conversion and calculation utilities
+- **URL Tools** - Full URL construction and parsing
+- **Date Tools** - Date expression resolution
+- **Help Tools** - Unified help system with topics
+- **Whoami Tools** - User identity across services
+- **PlantUML Tools** - Diagram validation and rendering
 
 **Note**: All data-heavy tools (search, list, get) **always** return buffered responses with metadata for origin tracking:
-- **JSON arrays**: Use `buffer_get_items` for complete items, `buffer_pipeline` for reports
+- **JSON arrays**: Use `buffer_get_items` for complete items, `buffer_transform` for reports
 - **XHTML**: Use `buffer_get_element` for element-based access
 - **Search**: Use `buffer_grep` to search within any buffer
 
@@ -49,7 +50,7 @@ JSON responses include `suggestedNextTools` based on context:
   "bufferId": "buf_xxx",
   "structure": { "type": "array", "itemCount": 500 },
   "suggestedNextTools": [
-    { "tool": "buffer_pipeline", "description": "Transform to table/report (98% token reduction)", "condition": "for Confluence reports" },
+    { "tool": "buffer_transform", "description": "Transform to table/report (98% token reduction)", "condition": "for Confluence reports" },
     { "tool": "buffer_get_items", "description": "Get complete items for AI analysis", "condition": "for detailed analysis" },
     { "tool": "buffer_grep", "description": "Search within results" }
   ]
@@ -111,7 +112,7 @@ When XHTML validation fails, the response includes element ID and suggested acti
 #### Jira Search → Confluence Report
 ```
 1. jira_search_issues(jql) → bufferId, suggestedNextTools
-2. buffer_pipeline(bufferId, pipeline) → tableBufferId (98% token reduction)
+2. buffer_transform(inputs, code) → tableBufferId (98% token reduction)
 3. confluence_edit(pageId) → pageBufferId, structure
 4. buffer_edit(pageBufferId, after=ID, fromBufferId=tableBufferId)
 5. confluence_draft_create(pageId, pageBufferId, autoRetry=true) → draft URL
@@ -121,7 +122,7 @@ When XHTML validation fails, the response includes element ID and suggested acti
 ```
 1. tempo_get_user_info() → workerKey
 2. tempo_get_worklogs(dateFrom, dateTo, workerKey) → bufferId, suggestedNextTools
-3. buffer_pipeline(bufferId, groupBy=project, sum=hours) → summaryBufferId
+3. buffer_transform(bufferId, groupBy=project, sum=hours) → summaryBufferId
 4. Use in report or display directly
 ```
 
@@ -137,7 +138,7 @@ When XHTML validation fails, the response includes element ID and suggested acti
 
 ---
 
-## Jira Tools (25)
+## Jira Tools (29)
 
 ### Localization / Non-English Jira
 
@@ -166,8 +167,8 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 1. jira_search_issues
-**Description**: Search for Jira issues using JQL. Auto-fetches all results (up to 5000).
+### jira_search_issues
+**Description**: Search for Jira issues using JQL. Auto-fetches all matching results.
 **Use Cases**: Find bugs, filter by status, search by assignee, complex queries
 
 | Parameter | Type | Required | Description |
@@ -180,7 +181,6 @@ The server automatically handles localized changelog field names for activity tr
 |-------|-------------|
 | `returnedItems` | Items available in buffer - **USE THIS** for actual count |
 | `jiraTotalMatching` | Total matching in Jira (may exceed returnedItems) |
-| `apiLimit` | Maximum items per search (5000 cap) |
 | `note` | Explanation when results are truncated |
 
 **Example Response** (when JQL matches 9998 issues):
@@ -189,16 +189,15 @@ The server automatically handles localized changelog field names for activity tr
   "bufferId": "buf_xxx",
   "returnedItems": 5000,
   "jiraTotalMatching": 9998,
-  "apiLimit": 5000,
   "note": "9998 issues match query, 5000 returned (API limit)"
 }
 ```
 
-**Returns**: `bufferId` with issues. Use `buffer_pipeline` for tables, `buffer_get_items` for AI analysis.
+**Returns**: `bufferId` with issues. Use `buffer_transform` for tables, `buffer_get_items` for AI analysis.
 
 ---
 
-### 2. jira_get_issue
+### jira_get_issue
 **Description**: Get detailed information about a specific issue
 **Use Cases**: View issue details, check status, read description and comments
 
@@ -212,7 +211,20 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 3. jira_create_issue
+### jira_get_issues
+**Description**: Get multiple Jira issues at once in a single buffer
+**Use Cases**: Batch fetch issues by key instead of calling jira_get_issue N times; compare issues side by side; bulk analysis
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| issueKeys | string \| string[] | ✓ | Single key or array of keys (e.g., "PROJ-123" or ["PROJ-123","PROJ-456"]) |
+| fields | string[] | ✗ | Specific fields to return |
+
+**Returns**: `bufferId` with flat issues array (same `jira_issue` schema as `jira_search_issues`). Use `buffer_transform` for tables, `buffer_get_items` for analysis.
+
+---
+
+### jira_create_issue
 **Description**: Create a new Jira issue
 **Use Cases**: Report bugs, create tasks, add stories to backlog
 
@@ -230,7 +242,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 4. jira_update_issue
+### jira_update_issue
 **Description**: Update fields on an existing issue
 **Use Cases**: Change priority, update description, modify assignee
 
@@ -245,7 +257,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 5. jira_transition_issue
+### jira_transition_issue
 **Description**: Move issue to different status
 **Use Cases**: Start work, mark as done, move to review
 
@@ -258,7 +270,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 6. jira_add_comment
+### jira_add_comment
 **Description**: Add a comment to an issue
 **Use Cases**: Provide updates, ask questions, document decisions
 
@@ -270,7 +282,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 7. jira_get_issue_comments
+### jira_get_issue_comments
 **Description**: Retrieve all comments from a Jira issue
 **Use Cases**: Read discussion history, check updates
 
@@ -283,7 +295,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 8. jira_list_projects
+### jira_list_projects
 **Description**: List all accessible Jira projects
 **Use Cases**: Discover available projects, get project keys
 
@@ -296,7 +308,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 9. jira_get_project
+### jira_get_project
 **Description**: Get detailed project information
 **Use Cases**: View project details, components, versions
 
@@ -309,7 +321,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 10. jira_get_issue_types
+### jira_get_issue_types
 **Description**: Get all available issue types in this Jira instance
 **Use Cases**: Discover type names before filtering by type in JQL, find localized or custom type names
 
@@ -321,29 +333,44 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 11. jira_get_fields
-**Description**: Get all available Jira fields (system and custom)
+### jira_get_fields
+**Description**: Get Jira fields (system and custom). Requires a search term or "all".
 **Use Cases**: Discover field names in user's language, find custom field IDs for JQL, identify Epic Link field
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
-| filter | enum | ✗ | Filter: "all" (default), "custom", "system", or "navigable" |
-| search | string | ✗ | Search in field name or ID (case-insensitive) |
+| search | string | **Yes** | `"all"` to return every field, or a search term to filter by name, id, clauseNames, or schemaType (case-insensitive) |
+| filter | enum | No | Filter by category: "all" (default), "custom", "system", or "navigable" |
 
 **Returns**: List of fields with id, name, custom, clauseNames, schemaType
 
 **Example workflow for Epic Link in any language**:
-1. Call `jira_get_fields(search="epic")` to find the Epic Link field
+1. Call `jira_get_fields(search="epic")` — matches name, id, clauseNames, AND schemaType
 2. Look for field with `schemaType = "com.pyxis.greenhopper.jira:gh-epic-link"`
-3. Use either:
-   - Localized name: `"Lien d'épopée" = PROJ-123` (French)
-   - Language-independent: `cf[10014] = PROJ-123`
+3. Use `cf[ID]` from clauseNames in JQL: `cf[10014] IS EMPTY`
 
-**Tip**: The `clauseNames` array shows all valid JQL names for a field. The `cf[ID]` syntax always works regardless of language.
+**Tip**: The `clauseNames` array shows all valid JQL names for a field. The `cf[ID]` syntax always works regardless of language. The search also matches `schemaType`, so `search="epic"` finds the Epic Link field even on French instances where it's named "Lien d'épopée".
 
 ---
 
-### 12. jira_get_transitions
+### jira_search_users
+**Description**: Search for Jira users by name, username, or email
+**Use Cases**: Find a person's username before building JQL queries with assignee/reporter
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| query | string | ✓ | Search text (display name, username, or email) |
+| maxResults | number | ✗ | Maximum results (default: 20) |
+
+**Returns**: Inline list of matching users with `key`, `name`, `displayName`, `emailAddress`.
+
+**Example workflow**:
+1. `jira_search_users(query="Fabien")` → finds users matching "Fabien"
+2. Use username in JQL: `assignee = "fthuillier"`
+
+---
+
+### jira_get_transitions
 **Description**: Get available workflow transitions for an issue
 **Use Cases**: Check what status changes are possible
 
@@ -353,7 +380,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 13. jira_link_issues
+### jira_link_issues
 **Description**: Create a link between two issues
 **Use Cases**: Mark blockers, relate issues, create dependencies
 
@@ -366,7 +393,28 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 14. jira_get_board
+### jira_list_boards
+**Description**: List all Jira Agile boards (Scrum and Kanban). Entry point for board discovery.
+**Use Cases**: Discover available boards, filter by project or type, find board IDs
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| projectKeyOrId | string | ✗ | Filter by project key or ID |
+| type | string | ✗ | Filter by board type ("scrum" or "kanban") |
+| name | string | ✗ | Filter by board name (contains) |
+
+**Returns**: `bufferId` with boards array. Each board has `id`, `name`, `type`, `projectKey`.
+
+**Examples**:
+```
+jira_list_boards()                         # All boards
+jira_list_boards(projectKeyOrId="PROJ")    # Boards for project
+jira_list_boards(type="scrum")             # Only Scrum boards
+```
+
+---
+
+### jira_get_board
 **Description**: Get Agile board information
 **Use Cases**: View board details, get board configuration
 
@@ -378,7 +426,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 15. jira_get_sprints
+### jira_get_sprints
 **Description**: List all sprints for a board
 **Use Cases**: View active sprints, check sprint schedules
 
@@ -391,7 +439,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 16. jira_get_sprint_issues
+### jira_get_sprint_issues
 **Description**: Get all issues in a specific sprint
 **Use Cases**: View sprint backlog, check sprint progress
 
@@ -403,7 +451,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 17. jira_get_issue_watchers
+### jira_get_issue_watchers
 **Description**: Get list of watchers on an issue
 **Use Cases**: See who's following an issue
 
@@ -413,7 +461,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 18. jira_get_issue_worklogs
+### jira_get_issue_worklogs
 **Description**: Retrieve all worklogs from a Jira issue
 **Use Cases**: Analyze time logged against an issue, see worklog history
 
@@ -425,7 +473,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 19. jira_get_total_worklogs
+### jira_get_total_worklogs
 **Description**: Get total worklogs for an issue and all its children recursively
 **Use Cases**: Get total time spent on an Epic including all stories and sub-tasks
 
@@ -437,7 +485,7 @@ The server automatically handles localized changelog field names for activity tr
 
 ---
 
-### 20. jira_list_epic_children
+### jira_list_epic_children
 **Description**: List all children of an Epic/Initiative without needing JQL
 **Use Cases**: Get Epic children, list Initiative epics, find issue hierarchy
 
@@ -460,7 +508,7 @@ Automatically detects Epic Link and Parent Link fields for language-independent
 
 ---
 
-### 21. jira_get_activity_digest
+### jira_get_activity_digest
 **Description**: Get recent activity across issues for LLM analysis. Returns DIRECTLY (not buffered).
 **Use Cases**: Project activity summary, team updates, blocker detection, weekly reports
 
@@ -471,7 +519,7 @@ Fetches comments, status changes, priority changes, and assignee changes - forma
 | projectKey | string | ✗ | Filter by project key |
 | jql | string | ✗ | Full JQL query for flexible scoping |
 | issueKeys | string[] | ✗ | Specific issue keys to include |
-| since | string | ✗ | Time range: "1d", "7d", "30d", or ISO date (default: "7d") |
+| since | string | ✗ | Time range: "7d", "30d", "365d", or ISO date (default: "30d"). Provide explicitly for accurate results. |
 | includeComments | boolean | ✗ | Include comments (default: true) |
 | includeStatusChanges | boolean | ✗ | Include status changes (default: true) |
 | includePriorityChanges | boolean | ✗ | Include priority changes (default: true) |
@@ -501,27 +549,27 @@ Fetches comments, status changes, priority changes, and assignee changes - forma
 
 ---
 
-### 22. jira_get_recent_comments
-**Description**: Get comments across multiple issues for discussion analysis. Returns DIRECTLY (not buffered).
-**Use Cases**: Discussion summaries, finding comments about specific topics, tracking team communication
+### jira_get_recent_comments
+**Description**: Get comments across multiple issues for analysis. Returns buffered data.
+**Use Cases**: Comment statistics (top commenters), discussion analysis, finding comments about specific topics
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
 | projectKey | string | ✗ | Filter by project key |
 | jql | string | ✗ | Full JQL query for flexible scoping |
 | issueKeys | string[] | ✗ | Specific issue keys to include |
-| since | string | ✗ | Time range: "1d", "7d", "30d", or ISO date (default: "7d") |
+| since | string | ✗ | Time range: "7d", "30d", "365d", or ISO date (default: "30d"). Provide explicitly for accurate results. |
 | authorKey | string | ✗ | Filter by comment author username |
-| maxComments | number | ✗ | Maximum comments to return (default: 30) |
-| includeContext | boolean | ✗ | Include issue summary/status (default: true) |
+| maxComments | number | ✗ | Maximum comments to return (default: all) |
 
 **At least one scoping parameter required**: `projectKey`, `jql`, or `issueKeys`
 
-**Returns**: Markdown-formatted comments grouped by issue with summary statistics.
+**Returns**: bufferId with `jira_comment` schema (issueKey, issueSummary, author, authorEmail, body, created, updated).
+**Next**: `buffer_transform` for stats/tables, `buffer_grep` to search comments.
 
 ---
 
-### 23. jira_get_changelog
+### jira_get_changelog
 **Description**: Get field changes across issues for tracking what happened. Returns DIRECTLY (not buffered).
 **Use Cases**: Status change tracking, priority escalation analysis, assignment history
 
@@ -530,7 +578,7 @@ Fetches comments, status changes, priority changes, and assignee changes - forma
 | projectKey | string | ✗ | Filter by project key |
 | jql | string | ✗ | Full JQL query for flexible scoping |
 | issueKeys | string[] | ✗ | Specific issue keys to include |
-| since | string | ✗ | Time range: "1d", "7d", "30d", or ISO date (default: "7d") |
+| since | string | ✗ | Time range: "7d", "30d", "365d", or ISO date (default: "30d"). Provide explicitly for accurate results. |
 | fields | string[] | ✗ | Fields to track (default: ["status", "priority", "assignee", "resolution"]) |
 | maxChanges | number | ✗ | Maximum changes to return (default: 50) |
 
@@ -551,7 +599,7 @@ Fetches comments, status changes, priority changes, and assignee changes - forma
 
 ---
 
-### 24. jira_analyze_epic
+### jira_analyze_epic
 **Description**: Comprehensive Epic/Feature analysis for LLM insights. Returns DIRECTLY (not buffered).
 **Use Cases**: Epic progress analysis, velocity tracking, time metrics, feature status
 
@@ -596,7 +644,7 @@ Currently **3 issues** are in progress.
 
 ---
 
-### 25. jira_epic_summary
+### jira_epic_summary
 **Description**: Lightweight Epic/Initiative summary with hierarchy and status breakdown. Returns DIRECTLY (not buffered).
 **Use Cases**: Quick Epic overview, status breakdown, cross-project dependencies
 
@@ -643,7 +691,7 @@ Provides quick overview without the heavy metrics of `jira_analyze_epic` - no ti
 
 ---
 
-### 26. jira_analyze_sprint
+### jira_analyze_sprint
 **Description**: Comprehensive Sprint analysis for LLM insights. Returns DIRECTLY (not buffered).
 **Use Cases**: Sprint progress, risk assessment, team workload, daily standups
 
@@ -730,11 +778,12 @@ Time tracking shows **71% of estimate used** for **65% completion**.
 
 ---
 
-## Confluence Tools (21)
+## Confluence Tools (20)
 
-### 1. confluence_search_content
+### confluence_search_content
 **Description**: Search Confluence content using CQL. Auto-fetches all results.
 **Use Cases**: Find pages, search by keyword, filter by space
+**CQL Syntax**: See `help(topic="cql")` for valid fields and examples.
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
@@ -745,7 +794,7 @@ Time tracking shows **71% of estimate used** for **65% completion**.
 
 ---
 
-### 2. confluence_get_page
+### confluence_get_page
 **Description**: Get a Confluence page by ID (PREFERRED when you have page ID)
 **Use Cases**: Read page content, prepare for editing
 
@@ -760,7 +809,7 @@ Time tracking shows **71% of estimate used** for **65% completion**.
 
 ---
 
-### 3. confluence_get_page_by_title
+### confluence_get_page_by_title
 **Description**: Get a page by title and space (use ONLY when you don't have page ID)
 **Use Cases**: Find page by name, access documentation
 
@@ -776,7 +825,7 @@ Time tracking shows **71% of estimate used** for **65% completion**.
 
 ---
 
-### 4. confluence_edit (RECOMMENDED)
+### confluence_edit (RECOMMENDED)
 **Description**: Smart page/draft loader - auto-resolves URLs, pageIds, draftIds, or SPACE/Title
 **Use Cases**: Edit any Confluence content with a single tool, handle URL input from users
 
@@ -826,7 +875,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 5. confluence_delete_page
+### confluence_delete_page
 **Description**: Delete a Confluence page
 **Use Cases**: Remove outdated content
 
@@ -836,7 +885,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 6. confluence_list_spaces
+### confluence_list_spaces
 **Description**: List all accessible Confluence spaces
 **Use Cases**: Discover available spaces, get space keys
 
@@ -848,7 +897,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 7. confluence_get_space
+### confluence_get_space
 **Description**: Get detailed information about a space
 **Use Cases**: View space details, get homepage
 
@@ -861,7 +910,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 8. confluence_get_page_children
+### confluence_get_page_children
 **Description**: Get all child pages of a page
 **Use Cases**: Navigate page hierarchy, list subpages
 
@@ -874,7 +923,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 9. confluence_add_comment
+### confluence_add_comment
 **Description**: Add a comment to a Confluence page
 **Use Cases**: Provide feedback, ask questions
 
@@ -885,7 +934,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 10. confluence_get_comments
+### confluence_get_comments
 **Description**: Get all comments on a Confluence page
 **Use Cases**: Read feedback, review discussions
 
@@ -897,7 +946,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 11. confluence_upload_attachment
+### confluence_upload_attachment
 **Description**: Upload an attachment to a Confluence page
 **Use Cases**: Attach documents, upload images
 
@@ -909,7 +958,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 12. confluence_list_attachments
+### confluence_list_attachments
 **Description**: List all attachments on a Confluence page
 **Use Cases**: View uploaded files, check attachments
 
@@ -921,23 +970,10 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 13. confluence_get_current_user_space
-**Description**: Get the current user's personal Confluence space
-**Use Cases**: Verify personal space before write operations, check space key for write-home restriction
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| (none) | | | |
-
-**Response includes**: `spaceKey`, `spaceName`, `spaceType`, `homePageId`, `homePageTitle`
-
-**Tip**: Use this to find your personal space key when write-home restriction is enabled.
-
----
-
-### 14. confluence_draft_list
-**Description**: List user's draft pages
+### confluence_draft_list
+**Description**: List user's UNPUBLISHED draft pages (work-in-progress content)
 **Use Cases**: View pending drafts, find drafts to continue editing
+**NOTE**: To find published pages you edited, use `confluence_search_content(cql="contributor=currentUser()")`
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
@@ -947,7 +983,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 15. confluence_draft_open
+### confluence_draft_open
 **Description**: Load existing draft into buffer for editing
 **Use Cases**: Continue editing a draft, prepare draft for publishing
 
@@ -961,7 +997,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 16. confluence_draft_create
+### confluence_draft_create
 **Description**: Create a draft for user review - either a new page or as an edit to an existing page
 **Use Cases**: Start new page as draft, edit existing page through draft workflow
 
@@ -1023,7 +1059,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 17. confluence_draft_save
+### confluence_draft_save
 **Description**: Save buffer content to draft (delete + recreate pattern)
 **Use Cases**: Checkpoint work, persist edits before publishing
 
@@ -1041,7 +1077,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 18. confluence_draft_delete
+### confluence_draft_delete
 **Description**: Permanently delete a draft
 **Use Cases**: Clean up abandoned drafts, remove unwanted content
 
@@ -1053,7 +1089,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 19. confluence_review_list
+### confluence_review_list
 **Description**: List all "[jicon-mcp REVIEW]" drafts for cleanup or management
 **Use Cases**: Find abandoned review drafts, manage multiple review workflows, clean up after publishing
 
@@ -1067,7 +1103,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 20. confluence_review_publish
+### confluence_review_publish
 **Description**: Publish a review draft to apply changes to the original page
 **Use Cases**: Apply reviewed changes to the original page, complete the review workflow
 
@@ -1087,7 +1123,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ---
 
-### 21. confluence_review_discard
+### confluence_review_discard
 **Description**: Discard a review draft without applying changes to the original page
 **Use Cases**: Cancel a review, abandon changes, clean up unwanted review drafts
 
@@ -1108,7 +1144,7 @@ buffer_edit(bufferId=pageBuffer, after=5, fromBufferId=newContentBuffer)
 
 ### JQL (Jira Query Language) Examples
 
-> **Note**: Type, status, and priority names below are in English. Use `jira_get_issue_types()` and `jira_get_fields()` to discover actual names for your Jira instance. Functions like `currentUser()`, `openSprints()`, `startOfDay()` work in all languages.
+> **Note**: Type, status, and priority names below are in English. Use `jira_get_issue_types()` and `jira_get_fields(search="epic")` to discover actual names for your Jira instance. Functions like `currentUser()`, `openSprints()`, `startOfDay()` work in all languages.
 
 ```jql
 # Find open bugs assigned to you
@@ -1212,7 +1248,7 @@ AND lastModified >= now("-30d")
 
 ## Tempo Tools (13)
 
-### 1. tempo_get_worklogs
+### tempo_get_worklogs
 **Description**: Get Tempo worklogs with filters
 **Use Cases**: View time entries, generate reports, review team work
 
@@ -1230,7 +1266,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 2. tempo_get_worklog
+### tempo_get_worklog
 **Description**: Get detailed information about a specific worklog entry
 **Use Cases**: View worklog details, check time logged
 
@@ -1242,7 +1278,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 3. tempo_log_work
+### tempo_log_work
 **Description**: Log time to a Jira issue
 **Use Cases**: Record work time, track daily activities
 
@@ -1257,7 +1293,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 4. tempo_update_worklog
+### tempo_update_worklog
 **Description**: Update an existing worklog entry
 **Use Cases**: Correct time logged, update descriptions
 
@@ -1273,7 +1309,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 5. tempo_delete_worklog
+### tempo_delete_worklog
 **Description**: Delete a worklog entry
 **Use Cases**: Remove incorrect entries
 
@@ -1283,7 +1319,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 6. tempo_get_accounts
+### tempo_get_accounts
 **Description**: Get all Tempo accounts
 **Use Cases**: List accounts for time tracking, find account keys
 
@@ -1295,7 +1331,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 7. tempo_get_account
+### tempo_get_account
 **Description**: Get detailed information about a Tempo account
 **Use Cases**: View account details, check status
 
@@ -1307,7 +1343,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 8. tempo_get_teams
+### tempo_get_teams
 **Description**: Get all Tempo teams
 **Use Cases**: List teams, find team IDs
 
@@ -1319,7 +1355,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 9. tempo_get_team
+### tempo_get_team
 **Description**: Get detailed information about a Tempo team
 **Use Cases**: View team details, check membership
 
@@ -1331,7 +1367,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 10. tempo_get_team_worklogs
+### tempo_get_team_worklogs
 **Description**: Get all worklogs for a team within a date range
 **Use Cases**: Team capacity reports, sprint reviews
 
@@ -1345,7 +1381,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 11. tempo_get_user_info
+### tempo_get_user_info
 **Description**: Get current user info (workerKey, username, accountId, displayName)
 **Use Cases**: Get workerKey for filtering worklogs, verify authentication
 
@@ -1357,7 +1393,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 12. tempo_get_epic_worklogs
+### tempo_get_epic_worklogs
 **Description**: Get all worklogs for an Epic and its child issues in one API call
 **Use Cases**: Epic time tracking, aggregate time reports, sprint cost analysis
 
@@ -1371,7 +1407,7 @@ AND lastModified >= now("-30d")
 
 ---
 
-### 13. tempo_get_top_worklogs
+### tempo_get_top_worklogs
 **Description**: Get top issues or users by workload for a period. Returns DIRECTLY (not buffered).
 **Use Cases**: Top tickets by workload, most active contributors, time distribution analysis
 
@@ -1402,22 +1438,22 @@ Aggregates Tempo worklogs and returns ranked results in markdown format.
 
 ---
 
-## Buffer Tools (11)
+## Buffer Tools (12)
 
 Buffer tools are used for local content management. All buffer operations are in-memory - write enforcement is on Jira/Confluence/Tempo tools.
 
 **XHTML Editing**: `buffer_edit` uses element IDs for precise positioning in XHTML content. Each element gets a unique ID when loaded - use `buffer_get_structure` to see them. `buffer_validate_xhtml` validates Confluence storage format. XHTML validation is also automatically applied before any Confluence write operation.
 
-**Data Pipelines**: `buffer_pipeline` transforms JSON buffers (from Jira/Tempo searches) with server-side filtering, grouping, sorting, and output generation - minimizing token usage.
+**Data Transformation**: `buffer_transform` transforms JSON buffers (from Jira/Tempo searches) with JavaScript code for filtering, grouping, sorting, and output generation - minimizing token usage.
 
-### 1. buffer_create
+### buffer_create
 **Description**: Create a new buffer with initial content. Returns bufferId and structure.
 
 **TIP**: Call `help(topic="storage")` for XHTML syntax. Call `help(topic="plantuml")` for diagram syntax.
 
 **Content types**:
 - **xhtml**: Confluence storage format. Returns element IDs for `buffer_edit`.
-- **json**: JSON data (array or object). Use `buffer_get_items` to access, `buffer_pipeline` to transform.
+- **json**: JSON data (array or object). Use `buffer_get_items` to access, `buffer_transform` to transform.
 
 **Use Cases**: Draft new Confluence pages, prepare content before persisting, create JSON arrays for aggregation
 
@@ -1464,7 +1500,7 @@ buffer_create({ content: [{"key":"PROJ-1"}], contentType: "json" })    // Native
 
 ---
 
-### 2. buffer_get_items
+### buffer_get_items
 **Description**: Retrieve items from a JSON buffer (arrays by index, objects by key).
 **Use Cases**: Iterate through search results, access object properties, process items in batches
 
@@ -1534,7 +1570,7 @@ buffer_get_items({ bufferId: "buf_xxx" })
 
 ---
 
-### 3. buffer_get_element
+### buffer_get_element
 **Description**: Get the raw XHTML content of a specific element by ID. Use to inspect problematic elements when fixing XHTML parsing errors.
 **Use Cases**: Debug XHTML validation errors, inspect element content before editing, targeted error recovery
 
@@ -1567,7 +1603,7 @@ buffer_get_element({
 
 ---
 
-### 4. buffer_set_items
+### buffer_set_items
 **Description**: Update or append items in a JSON buffer (arrays by ID/append, objects by key).
 **Use Cases**: Modify JSON data after processing, update specific fields, append new items to arrays, merge new data into objects
 
@@ -1631,19 +1667,19 @@ buffer_set_items({
 
 ---
 
-### 5. buffer_list
-**Description**: List all active buffers with their metadata
-**Use Cases**: View active buffers, check expiration times
+### buffer_list
+**Description**: List all active buffers with their metadata. Buffers are cleaned up when session ends. Max buffers per session configurable via JICON_MAX_BUFFERS (default: 10); oldest unmodified evicted first when full.
+**Use Cases**: View active buffers, recover lost buffer IDs
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
 | (none) | | | |
 
-**Response includes**: `count`, list of buffers with `bufferId`, `totalSize`, `createdAt`, `expiresAt`, `metadata`
+**Response includes**: `count`, list of buffers with `bufferId`, `totalSize`, `createdAt`, `metadata`
 
 ---
 
-### 6. buffer_clear
+### buffer_clear
 **Description**: Clear a specific buffer or all buffers
 **Use Cases**: Free up memory, clean up after processing
 
@@ -1655,7 +1691,7 @@ buffer_set_items({
 
 ---
 
-### 7. buffer_grep
+### buffer_grep
 **Description**: Search buffered content for patterns. Supports regex, context lines (-A/-B/-C), and case-insensitive (-i). Large results are buffered.
 **Use Cases**: Find specific content in large responses, locate text for editing
 
@@ -1677,253 +1713,228 @@ buffer_set_items({
 
 ---
 
-### 8. buffer_pipeline
-**Description**: Transform JSON buffer data with a declarative pipeline: select fields, filter, group/aggregate, sort, format, and output to various formats.
-**Use Cases**: Server-side data transformation to minimize token usage, generate XHTML tables for Confluence, export to CSV/Markdown, aggregate statistics
+### buffer_transform
+**Description**: Execute JavaScript code in a secure QuickJS sandbox to transform buffer data.
+**Use Cases**: Server-side data transformation with full JavaScript expressiveness, generate XHTML tables for Confluence, custom filtering/grouping/aggregation
 
-**Token Efficiency**: A pipeline that filters, sorts, and outputs a table executes in **1 tool call** instead of iterating through items. For pure data transforms, this achieves **98% token reduction**.
-
-**Schema Quick Reference:**
-```json
-{
-  "sourceBufferId": "buf_xxx",
-  "pipeline": {
-    "select": { "fields": [...] },
-    "filter": [...],
-    "groupBy": { "field": "...", "aggregations": [...] },
-    "sort": [...],
-    "limit": 10,
-    "format": [...],
-    "output": { "type": "xhtml_table", "table": {...} }
-  }
-}
-```
-
-**Common Mistakes:**
-
-| Wrong | Correct | Why |
-|-------|---------|-----|
-| `sortBy: [...]` | `sort: [...]` | Key name is "sort" not "sortBy" |
-| `transform: "map"` | `transform: "date"` | Valid: uppercase, lowercase, date, number, boolean, string |
-| No `output` | `output: {...}` | Required field - pipeline must have output |
-| `pipeline: "{...}"` | `pipeline: {...}` | Must be object, not JSON string |
-| After select: `sort: [{field: "issueType"}]` | `sort: [{field: "Type"}]` | After `select` renames "issueType" to "Type", use NEW name |
+**Token Efficiency**: A transformation generates complete output in **1 tool call** instead of iterating through items. For pure data transforms, this achieves **98% token reduction**.
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
-| bufferId | string | ✓ | Source buffer ID containing JSON array |
-| pipeline | object | ✓ | Pipeline definition (see below) |
+| inputs | object | ✓ | Map of variable name to buffer ID. Example: `{ issues: "buf_abc123" }` |
+| code | string | ✓ | JavaScript code to execute (ES2020, synchronous). Access inputs as globals, return value becomes output buffer. |
+| limits | object | ✗ | Optional `{ timeout: 5000, memory: 50000000 }` (default: 5s, 50MB) |
 
-**Type Requirement**: Buffer must have `contentType: "json"`. Returns error if buffer is XHTML or plain text.
+**Type Requirement**: All input buffers must have `contentType: "json"`. Returns error if buffer is XHTML or plain text.
 
-**Pipeline Definition:**
+**Built-in Helper Functions (available as globals):**
 
-```typescript
-{
-  // Stage 1: Select specific fields (optional)
-  select?: {
-    fields: [
-      { from: "key" },                           // Keep field as-is
-      { from: "priority.name", as: "Priority" }, // Rename field
-      { from: "created", transform: "date" }     // Transform value
-    ]
-  },
+| Category | Function | Description |
+|----------|----------|-------------|
+| **Aggregation** | `groupBy(array, keyOrFn)` | Group array by field or function → `{ key: items[] }` |
+| | `sum(array, field?)` | Sum numeric values |
+| | `avg(array, field?)` | Average numeric values |
+| | `min(array, field?)` | Minimum value |
+| | `max(array, field?)` | Maximum value |
+| | `count(array)` | Count items |
+| | `unique(array, field?)` | Unique values |
+| **Object** | `get(obj, 'path.to.field')` | Deep get with dot notation |
+| | `pick(obj, ['a', 'b'])` | Pick specific keys |
+| | `omit(obj, ['a'])` | Omit specific keys |
+| **Date** | `parseDate(string)` | Parse date → timestamp (ms) |
+| | `formatDate(ts, fmt?)` | Format timestamp (fmt: 'date', 'time', 'datetime', 'iso') |
+| | `daysBetween(d1, d2)` | Days between two dates |
+| **Output** | `toTable(array, config)` | Generate Confluence XHTML table |
+| | `toList(array, config)` | Generate Confluence XHTML list |
+| | `toMarkdownTable(array, config)` | Generate Markdown table |
+| | `toMarkdownList(array, config)` | Generate Markdown list |
 
-  // Stage 2: Filter items (optional, AND logic between conditions)
-  filter?: [
-    { field: "status.name", operator: "ne", value: "Done" },
-    { field: "priority.name", operator: "in", value: ["High", "Critical"] }
-  ],
+**Context Variables (for link generation):**
+- `JIRA_URL` - Jira base URL (from server config)
+- `CONFLUENCE_URL` - Confluence base URL (from server config)
 
-  // Stage 3: Group and aggregate (optional)
-  groupBy?: {
-    field: "assignee.displayName",
-    aggregations: [
-      { function: "count", as: "totalIssues" },
-      { function: "sum", field: "timeSpent", as: "totalTime" },
-      { function: "list", field: "key", as: "issueKeys" }
-    ]
-  },
+**toTable() Configuration:**
 
-  // Stage 4: Sort results (optional)
-  sort?: [
-    { field: "priority.name", direction: "asc" },
-    { field: "key", direction: "desc" }
+```javascript
+toTable(array, {
+  title: 'Table Title',           // Optional h2 above table
+  showRowNumbers: true,           // Add # column
+  tableClass: 'confluenceTable',  // CSS class
+  columns: [
+    { field: 'key', header: 'Issue', link: { type: 'jira' } },
+    { field: 'summary', header: 'Summary', width: '40%' },
+    { field: 'priority.name', header: 'Priority', align: 'center' }
   ],
-
-  // Stage 5: Limit results (optional)
-  limit?: 50,
-
-  // Stage 6: Conditional formatting (optional)
-  format?: [
+  format: [  // Conditional styling
     {
-      condition: { field: "priority.name", operator: "eq", value: "High" },
-      style: { color: "#dc3545", bold: true }
-    },
-    {
-      condition: { field: "status.name", operator: "eq", value: "Done" },
-      style: { color: "#28a745", icon: "✓" }
+      condition: { field: 'priority.name', operator: 'eq', value: 'Blocker' },
+      style: { color: '#d04437', bold: true, icon: '🔴' },
+      fields: ['priority.name']  // Apply to specific fields (or omit for row)
     }
-  ],
+  ]
+})
+```
 
-  // Stage 7: Output configuration (REQUIRED)
-  output: {
-    type: "xhtml_table",  // or "xhtml_list", "json", "csv", "markdown"
-    table: {
-      title: "Open Issues",
-      columns: [
-        { field: "key", header: "Issue", link: { type: "jira" } },
-        { field: "summary", header: "Summary" },
-        { field: "priority.name", header: "Priority" }
-      ]
+**toList() Configuration:**
+
+```javascript
+toList(array, {
+  title: 'List Title',
+  style: 'bullet',  // 'bullet', 'numbered', 'none'
+  template: '{{key}}: {{summary}} ({{assignee.displayName}})'
+})
+```
+
+**toMarkdownTable() Configuration:**
+
+```javascript
+toMarkdownTable(array, {
+  title: 'Table Title',           // Optional ## heading
+  showRowNumbers: true,           // Add # column
+  columns: [
+    { field: 'key', header: 'Issue', link: { type: 'jira' } },
+    { field: 'summary', header: 'Summary' },
+    { field: 'priority.name', header: 'Priority', align: 'center' }
+  ],
+  format: [  // Conditional styling (bold/italic in Markdown)
+    {
+      condition: { field: 'priority.name', operator: 'eq', value: 'Blocker' },
+      style: { bold: true, icon: '🔴' },
+      fields: ['priority.name']
     }
-  }
-}
+  ]
+})
+// Returns: { __markdown: true, content: "| # | Issue | Summary |..." }
 ```
 
-**Filter Operators:**
-
-| Operator | Description | Example |
-|----------|-------------|---------|
-| `eq` | Equals | `{ field: "status.name", operator: "eq", value: "Open" }` |
-| `ne` | Not equals | `{ field: "status.name", operator: "ne", value: "Done" }` |
-| `gt`, `lt`, `gte`, `lte` | Numeric comparison | `{ field: "priority.id", operator: "gt", value: 2 }` |
-| `contains` | Substring match (case-insensitive) | `{ field: "summary", operator: "contains", value: "bug" }` |
-| `startsWith`, `endsWith` | String prefix/suffix | `{ field: "key", operator: "startsWith", value: "PROJ-" }` |
-| `in`, `notIn` | Value in array | `{ field: "priority.name", operator: "in", value: ["High", "Critical"] }` |
-| `exists`, `notExists` | Field presence | `{ field: "assignee", operator: "exists" }` |
-| `empty`, `notEmpty` | Empty string/array/null | `{ field: "labels", operator: "notEmpty" }` |
-| `regex` | Regular expression | `{ field: "summary", operator: "regex", value: "^\\[BUG\\]" }` |
-
-**Aggregation Functions:**
-
-| Function | Description | Requires `field` |
-|----------|-------------|------------------|
-| `count` | Count items in group | No |
-| `sum` | Sum numeric values | Yes |
-| `avg` | Average numeric values | Yes |
-| `min`, `max` | Min/max numeric values | Yes |
-| `first`, `last` | First/last value | Yes |
-| `list` | Collect all values | Yes |
-| `unique` | Unique values | Yes |
-
-**Output Types:**
-
-| Type | Description | Config |
-|------|-------------|--------|
-| `xhtml_table` | Confluence-compatible table | `table: { title?, columns: [...], showRowNumbers? }` |
-| `xhtml_list` | Confluence-compatible list | `list: { title?, template: "{{key}}: {{summary}}", style?: "bullet"|"numbered"|"none" }` |
-| `json` | Clean JSON array | `includeMetadata?: boolean` |
-| `csv` | CSV with headers | `table: { columns: [...] }` |
-| `markdown` | Markdown table | `table: { columns: [...] }` |
-
-**Column Configuration:**
+**toMarkdownList() Configuration:**
 
-```typescript
-{
-  field: "key",                    // Field path (dot notation)
-  header: "Issue",                 // Column header text
-  link?: { type: "jira" },         // Auto-link (jira, confluence, url)
-  width?: "100px",                 // Column width
-  align?: "left" | "center" | "right"
-}
+```javascript
+toMarkdownList(array, {
+  title: 'List Title',
+  style: 'bullet',    // 'bullet', 'numbered', 'task'
+  template: '{{key}}: {{summary}} ({{assignee.displayName}})'
+})
+// Returns: { __markdown: true, content: "- PROJ-1: Fix bug..." }
 ```
 
-**Response includes**: `bufferId` (new output buffer), `inputItems`, `outputItems`, `pipelineStages`, `outputType`, `preview`, `bufferSizeBytes`, `structure` (for XHTML), `hint`
+**Link Types:**
+- `jira` - Auto-links to Jira issue using `key` field
+- `confluence` - Links to Confluence page by ID
+- `custom` - Custom URL template with `{{field}}` placeholders
+
+**Format Condition Operators:** `eq`, `ne`, `gt`, `lt`, `gte`, `lte`, `contains`, `startsWith`, `endsWith`, `in`, `notIn`, `exists`, `notExists`, `regex`, `empty`, `notEmpty`
+
+**Response includes**: `bufferId` (new output buffer), `contentType` (json, xhtml, or markdown), `itemCount` (for arrays), `hint`
 
 **Example - Filter and output table:**
-```typescript
+```javascript
 // Search returns bufferId with 500 issues
 jira_search_issues({ jql: "project = PROJ" })
 // -> { bufferId: "buf_issues", structure: { itemCount: 500 } }
 
 // Transform in ONE call (instead of iterating 500 items)
-buffer_pipeline({
-  bufferId: "buf_issues",
-  pipeline: {
-    filter: [
-      { field: "issuetype.name", operator: "eq", value: "Bug" },
-      { field: "status.name", operator: "ne", value: "Done" }
-    ],
-    sort: [{ field: "priority.name", direction: "asc" }],
-    limit: 20,
-    format: [
-      { condition: { field: "priority.name", operator: "eq", value: "High" },
-        style: { color: "#dc3545", bold: true } }
-    ],
-    output: {
-      type: "xhtml_table",
-      table: {
-        title: "Top 20 Open Bugs",
-        columns: [
-          { field: "key", header: "Issue", link: { type: "jira" } },
-          { field: "summary", header: "Summary" },
-          { field: "priority.name", header: "Priority" },
-          { field: "assignee.displayName", header: "Assignee" }
-        ]
-      }
-    }
-  }
+buffer_transform({
+  inputs: { issues: "buf_issues" },
+  code: `
+    const bugs = issues.filter(i =>
+      i.issuetype?.name === 'Bug' &&
+      i.status?.name !== 'Done'
+    );
+    bugs.sort((a, b) => (a.priority?.id || 0) - (b.priority?.id || 0));
+    const top20 = bugs.slice(0, 20);
+
+    return toTable(top20, {
+      title: 'Top 20 Open Bugs',
+      columns: [
+        { field: 'key', header: 'Issue', link: { type: 'jira' } },
+        { field: 'summary', header: 'Summary' },
+        { field: 'priority.name', header: 'Priority' },
+        { field: 'assignee.displayName', header: 'Assignee' }
+      ],
+      format: [
+        { condition: { field: 'priority.name', operator: 'eq', value: 'High' },
+          style: { color: '#dc3545', bold: true } }
+      ]
+    });
+  `
 })
-// -> { bufferId: "buf_result", outputItems: 15, preview: "<table>...", structure: [...] }
+// -> { bufferId: "buf_result", contentType: "xhtml" }
 ```
 
-**Example - Group by assignee with aggregations:**
-```typescript
-buffer_pipeline({
-  bufferId: "buf_issues",
-  pipeline: {
-    filter: [{ field: "status.name", operator: "ne", value: "Done" }],
-    groupBy: {
-      field: "assignee.displayName",
-      aggregations: [
-        { function: "count", as: "issueCount" },
-        { function: "list", field: "key", as: "issues" }
+**Example - Group by assignee with statistics:**
+```javascript
+buffer_transform({
+  inputs: { issues: "buf_issues" },
+  code: `
+    const open = issues.filter(i => i.status?.name !== 'Done');
+    const byAssignee = groupBy(open, 'assignee.displayName');
+
+    const stats = Object.entries(byAssignee).map(([name, items]) => ({
+      assignee: name || 'Unassigned',
+      count: items.length,
+      issues: items.map(i => i.key).join(', ')
+    }));
+
+    stats.sort((a, b) => b.count - a.count);
+
+    return toTable(stats, {
+      title: 'Issues by Assignee',
+      columns: [
+        { field: 'assignee', header: 'Assignee' },
+        { field: 'count', header: 'Count', align: 'right' },
+        { field: 'issues', header: 'Issue Keys' }
       ]
-    },
-    sort: [{ field: "issueCount", direction: "desc" }],
-    output: {
-      type: "xhtml_table",
-      table: {
-        title: "Issues by Assignee",
-        columns: [
-          { field: "displayName", header: "Assignee" },
-          { field: "issueCount", header: "Count" },
-          { field: "issues", header: "Issues" }
-        ]
-      }
-    }
-  }
+    });
+  `
 })
 ```
 
-**Example - Export to CSV:**
-```typescript
-buffer_pipeline({
-  bufferId: "buf_issues",
-  pipeline: {
-    select: {
-      fields: [
-        { from: "key" },
-        { from: "summary" },
-        { from: "status.name", as: "Status" },
-        { from: "created", transform: "date" }
+**Example - Return JSON for further processing:**
+```javascript
+buffer_transform({
+  inputs: { issues: "buf_issues" },
+  code: `
+    const summary = issues.map(i => ({
+      key: i.key,
+      summary: i.summary,
+      status: i.status?.name,
+      priority: i.priority?.name
+    }));
+    return summary;  // Returns JSON buffer, not XHTML
+  `
+})
+// -> { bufferId: "buf_result", contentType: "json", itemCount: 500 }
+```
+
+**Example - Markdown table output:**
+```javascript
+buffer_transform({
+  inputs: { issues: "buf_issues" },
+  code: `
+    const open = issues.filter(i => i.status?.name !== 'Done');
+    return toMarkdownTable(open.slice(0, 20), {
+      title: 'Open Issues',
+      columns: [
+        { field: 'key', header: 'Issue', link: { type: 'jira' } },
+        { field: 'summary', header: 'Summary' },
+        { field: 'status.name', header: 'Status' },
+        { field: 'priority.name', header: 'Priority', align: 'center' }
+      ],
+      format: [
+        { condition: { field: 'priority.name', operator: 'eq', value: 'High' },
+          style: { bold: true, icon: '🔴' } }
       ]
-    },
-    output: {
-      type: "csv",
-      table: {
-        columns: [
-          { field: "key", header: "Issue" },
-          { field: "summary", header: "Summary" },
-          { field: "Status", header: "Status" },
-          { field: "created", header: "Created" }
-        ]
-      }
-    }
-  }
+    });
+  `
 })
-// -> { bufferId: "buf_csv", output: "Issue,Summary,Status,Created\nPROJ-1,..." }
+// -> { bufferId: "buf_result", contentType: "markdown" }
+// Output:
+// ## Open Issues
+//
+// | Issue | Summary | Status | Priority |
+// | --- | --- | --- | :--: |
+// | [PROJ-1](https://jira.example.com/browse/PROJ-1) | Fix login bug | Open | 🔴 **High** |
 ```
 
 **Common Jira Fields:**
@@ -1932,12 +1943,12 @@ buffer_pipeline({
 - `assignee.displayName`, `reporter.displayName`
 - `created`, `updated`, `resolutiondate`
 - `labels` (array), `components[].name`
-- `timeoriginalestimate`, `timeestimate`, `timespent`
+- `timeoriginalestimate`, `timeestimate`, `timespent` (often null — use `buffer_get_schema` to check `optional` flag)
 
 **Workflow - Jira to Confluence table:**
 ```
 1. jira_search_issues(jql) → bufferId with JSON
-2. buffer_pipeline(bufferId, pipeline) → bufferId with XHTML table
+2. buffer_transform(inputs, code) → bufferId with XHTML table
 3. confluence_edit(pageId) → page bufferId
 4. buffer_edit(pageBufferId, after=ID, fromBufferId=tableBufferId)
 5. confluence_draft_create(pageId, pageBufferId) → draft for review
@@ -1945,7 +1956,7 @@ buffer_pipeline({
 
 ---
 
-### 9. buffer_edit
+### buffer_edit
 **Description**: Edit buffer content. For XHTML: use element IDs (single or batch). For plain/json: use string replacement or append.
 **Use Cases**: Insert/replace/remove elements in Confluence pages, modify Jira/Tempo content, compose content from multiple buffers
 
@@ -2077,7 +2088,7 @@ confluence_draft_create({ pageId: "123", bufferId: "buf_A" })
 
 ---
 
-### 10. buffer_get_structure
+### buffer_get_structure
 **Description**: Get current element structure for an XHTML buffer
 **Use Cases**: View element IDs for editing, understand document structure
 
@@ -2111,7 +2122,7 @@ buffer_get_structure({ bufferId: "buf_xxx" })
 
 ---
 
-### 11. buffer_validate_xhtml
+### buffer_validate_xhtml
 **Description**: Validate buffered content as Confluence storage format (XHTML)
 **Use Cases**: Check content validity before writing, debug validation errors
 
@@ -2139,11 +2150,95 @@ buffer_get_structure({ bufferId: "buf_xxx" })
 
 ---
 
+### buffer_get_schema
+**Description**: Get the schema for a JSON buffer. Returns field names, types, and sample values from the actual data.
+**Use Cases**: Understand buffer structure before writing `buffer_transform` code, discover available fields for data processing
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| bufferId | string | ✓ | Buffer ID to get schema for |
+
+**Type Requirement**: Buffer must have `contentType: "json"`. Returns error if buffer is XHTML.
+
+**Schema Types**: Buffers from API tools have a named schema type (e.g., `jira_issue`, `tempo_worklog`, `confluence_page`). The schema defines all available fields with consistent structure.
+
+**Available Schema Types**:
+| Schema Type | Tools That Return It |
+|-------------|---------------------|
+| `jira_issue` | `jira_search_issues`, `jira_get_issue`, `jira_get_issues`, `jira_list_epic_children`, `jira_get_sprint_issues` |
+| `jira_comment` | `jira_get_issue_comments` |
+| `jira_project` | `jira_list_projects`, `jira_get_project` |
+| `jira_board` | `jira_get_board` |
+| `jira_sprint` | `jira_get_sprints` |
+| `jira_worklog` | `jira_get_issue_worklogs` |
+| `jira_worklog_total` | `jira_get_total_worklogs` |
+| `tempo_worklog` | `tempo_get_worklogs`, `tempo_get_worklog`, `tempo_get_team_worklogs`, `tempo_get_epic_worklogs` |
+| `tempo_account` | `tempo_get_accounts`, `tempo_get_account` |
+| `tempo_team` | `tempo_get_teams`, `tempo_get_team` |
+| `confluence_page` | `confluence_search_content`, `confluence_get_page_children` |
+| `confluence_space` | `confluence_list_spaces`, `confluence_get_space` |
+| `confluence_comment` | `confluence_get_comments` |
+| `confluence_attachment` | `confluence_list_attachments` |
+| `confluence_draft` | `confluence_draft_list` |
+
+**Response includes**: `bufferId`, `schemaType`, `description`, `itemCount` (for arrays), `legend` (property definitions), `fields` (with type, required, optional, searchable, writable, jqlName, description, sample)
+
+**Field Properties**:
+| Property | Meaning |
+|----------|---------|
+| `required` | Always present with a non-null value |
+| `optional` | May be null when not set — use `== null` to check |
+| `searchable` | Can be used in JQL/CQL queries |
+| `writable` | Can be set via update API |
+| `jqlName` | JQL clause name when different from field name (e.g., `type` → `issuetype`) |
+
+**Example - Get schema before writing transform code:**
+```typescript
+// 1. Search returns bufferId with schemaType in response
+jira_search_issues({ jql: "project=PROJ" })
+// Returns: { bufferId: "buf_xxx", schemaType: "jira_issue", fields: ["key", "summary", "status", ...] }
+
+// 2. Get detailed schema with samples
+buffer_get_schema({ bufferId: "buf_xxx" })
+// Returns: {
+//   bufferId: "buf_xxx",
+//   schemaType: "jira_issue",
+//   description: "Jira issue with core fields flattened for easy access",
+//   itemCount: 45,
+//   legend: { required: "Always present...", optional: "May be null...", ... },
+//   fields: {
+//     key: { type: "string", required: true, searchable: true, description: "Issue key (e.g., PROJ-123)", sample: "PROJ-123" },
+//     summary: { type: "string", required: true, searchable: true, writable: true, description: "Issue title/summary", sample: "Fix login bug" },
+//     status: { type: "string", required: true, searchable: true, description: "Current status name", sample: "In Progress" },
+//     type: { type: "string", required: true, searchable: true, writable: true, jqlName: "issuetype", description: "Issue type name", sample: "Bug" },
+//     assignee: { type: "string", required: false, optional: true, searchable: true, writable: true, description: "Assignee display name", sample: "John Doe" },
+//     ...
+//   }
+// }
+
+// 3. Now write accurate transform code using flat field names
+buffer_transform({
+  inputs: [{ bufferId: "buf_xxx" }],
+  code: `return toMarkdownTable(issues, {
+    columns: [
+      { field: 'key', header: 'Key' },
+      { field: 'summary', header: 'Summary' },
+      { field: 'status', header: 'Status' },
+      { field: 'assignee', header: 'Assignee' }
+    ]
+  });`
+})
+```
+
+**Key Benefit**: All tools returning the same schemaType produce identical field structure. Once you learn `jira_issue` fields, the same structure works for `jira_search_issues`, `jira_get_issue`, `jira_list_epic_children`, and `jira_get_sprint_issues`.
+
+---
+
 ## Workload Tools (2)
 
 Utility tools for time calculations. Always available with any Jira, Confluence, or Tempo action.
 
-### 1. workload_convert
+### workload_convert
 **Description**: Convert workload time between units (seconds, hours, days)
 **Use Cases**: Convert time values for display, calculate work estimates
 
@@ -2157,7 +2252,7 @@ Utility tools for time calculations. Always available with any Jira, Confluence,
 
 ---
 
-### 2. workload_sum
+### workload_sum
 **Description**: Sum multiple workload values and return total in all units
 **Use Cases**: Calculate total time from multiple entries, aggregate worklogs
 
@@ -2174,7 +2269,7 @@ Utility tools for time calculations. Always available with any Jira, Confluence,
 
 Utility tools for URL construction and parsing. Always available with any Jira, Confluence, or Tempo action.
 
-### 1. fullurl
+### fullurl
 **Description**: Convert Jira issue keys, Confluence page IDs, or relative paths into full URLs
 **Use Cases**: Generate clickable links for display, resolve relative Confluence paths
 
@@ -2203,7 +2298,7 @@ fullurl("/display/DOCS/Home") // → https://confluence.example.com/display/DOCS
 
 ---
 
-### 2. parseurl
+### parseurl
 **Description**: Parse a Jira or Confluence URL to extract identifiers (pageId, issueKey, draftId, etc.)
 **Use Cases**: Extract IDs from URLs users share, prepare input for other tools
 
@@ -2238,7 +2333,7 @@ fullurl("/display/DOCS/Home") // → https://confluence.example.com/display/DOCS
 
 Unified help system for all Jicon workflows and syntax guides. Always available with any Jira, Confluence, or Tempo action.
 
-### 1. help
+### help
 **Description**: Get Jicon MCP Server help - workflows and syntax guides
 **Use Cases**: Learn workflows, understand tool sequences, get syntax references
 
@@ -2284,7 +2379,7 @@ help(topic="analysis")       // LLM analysis tools guide
 
 Date resolution utility for pre-computing date ranges. Always available with any Jira, Confluence, or Tempo action.
 
-### 1. date_resolve
+### date_resolve
 **Description**: Resolve date expressions to concrete dates with business day counts
 **Use Cases**: Pre-compute date ranges for reports, time tracking, activity analysis
 
@@ -2332,6 +2427,50 @@ date_resolve(expression="this_month") // Current month to date
 
 ---
 
+## Whoami Tools (1)
+
+Unified user identity across all configured services.
+
+### whoami
+**Description**: Get the currently authenticated user from all configured services
+**Use Cases**: Verify credentials, get user keys for queries, check access across services
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| (none) | | | |
+
+**Returns**: User info from each configured service:
+```json
+{
+  "jira": {
+    "key": "JIRAUSER12345",
+    "name": "john.doe",
+    "displayName": "John Doe",
+    "emailAddress": "john.doe@example.com"
+  },
+  "confluence": {
+    "userKey": "JIRAUSER12345",
+    "username": "john.doe",
+    "displayName": "John Doe",
+    "personalSpace": {
+      "spaceKey": "~johndoe",
+      "spaceName": "John Doe",
+      "spaceType": "personal",
+      "homePageId": "123456",
+      "homePageTitle": "John Doe's Home"
+    }
+  }
+}
+```
+
+**Notes**:
+- Returns info from each configured service (Jira, Confluence)
+- Includes Confluence personal space info (for write-home restriction)
+- Errors are collected in `errors` array if any service fails
+- Available in all permission modes (readonly, full, custom)
+
+---
+
 ## PlantUML Tools (3)
 
 PlantUML validation and rendering via external server. Configure with `JICON_PLANTUML_SERVER_URL` environment variable.
@@ -2348,7 +2487,7 @@ PlantUML validation and rendering via external server. Configure with `JICON_PLA
 ```
 Include expansion is enabled by default. Whitelisted URLs: `plantuml-stdlib/*`, `plantuml/*`, `awslabs/aws-icons-for-plantuml/*`. See `help(topic="plantuml")` for examples.
 
-### 1. plantuml_validate
+### plantuml_validate
 **Description**: Validate PlantUML diagram syntax using a real PlantUML server
 **Use Cases**: Check diagram syntax before inserting into Confluence, debug diagram errors
 
@@ -2363,7 +2502,7 @@ Include expansion is enabled by default. Whitelisted URLs: `plantuml-stdlib/*`,
 
 ---
 
-### 2. plantuml_render
+### plantuml_render
 **Description**: Render PlantUML diagram to a specified format
 **Use Cases**: Generate ASCII art for terminal display, create images for documentation
 
@@ -2390,7 +2529,7 @@ plantuml_render({
 
 ---
 
-### 3. plantuml_status
+### plantuml_status
 **Description**: Check PlantUML server status
 **Use Cases**: Verify PlantUML server is available, troubleshoot connection issues
 
@@ -2426,7 +2565,7 @@ All data-heavy tools (search, list, get) **always** return buffered responses wi
     "title": "JQL: project = PROJ"
   },
   "accessors": {
-    "pipeline": { "tool": "buffer_pipeline", "description": "Transform to table/CSV/list" },
+    "transform": { "tool": "buffer_transform", "description": "Transform with JavaScript code" },
     "get_items": { "tool": "buffer_get_items", "description": "Get complete items for analysis" },
     "search": { "tool": "buffer_grep", "description": "Search within buffer" }
   }
@@ -2439,7 +2578,7 @@ All data-heavy tools (search, list, get) **always** return buffered responses wi
 - `contentType`: Buffer type (`json`, `xhtml`, `plain`)
 
 **Working with JSON Buffers (Jira/Tempo):**
-- `buffer_pipeline(bufferId, pipeline)` - Transform to table/CSV/list (98% token reduction)
+- `buffer_transform(inputs, code)` - Transform with JavaScript code (98% token reduction)
 - `buffer_get_items(bufferId, start, count)` - Get complete items for AI analysis
 - `buffer_grep(bufferId, pattern)` - Search within buffered data
 
@@ -2449,7 +2588,7 @@ All data-heavy tools (search, list, get) **always** return buffered responses wi
 - `buffer_grep(bufferId, pattern)` - Search within buffered data
 
 **Always-Buffered Tools:**
-- **Jira**: `jira_search_issues`, `jira_get_issue`, `jira_list_projects`, `jira_get_project`, `jira_get_board`, `jira_get_sprints`, `jira_get_sprint_issues`, `jira_get_issue_comments`, `jira_get_issue_worklogs`, `jira_get_total_worklogs`
+- **Jira**: `jira_search_issues`, `jira_get_issue`, `jira_get_issues`, `jira_list_projects`, `jira_get_project`, `jira_get_board`, `jira_get_sprints`, `jira_get_sprint_issues`, `jira_get_issue_comments`, `jira_get_issue_worklogs`, `jira_get_total_worklogs`
 - **Confluence**: `confluence_search_content`, `confluence_list_spaces`, `confluence_get_space`, `confluence_get_page_children`, `confluence_get_comments`, `confluence_list_attachments`, `confluence_draft_list`
 - **Tempo**: `tempo_get_worklogs`, `tempo_get_worklog`, `tempo_get_accounts`, `tempo_get_account`, `tempo_get_teams`, `tempo_get_team`, `tempo_get_team_worklogs`, `tempo_get_epic_worklogs`
 
@@ -2506,25 +2645,25 @@ Tools enforce type-safe buffer access - each tool only accepts buffers of the ty
 
 | Buffer Type | Tools That REQUIRE This Type |
 |-------------|------------------------------|
-| **json** | `buffer_pipeline`, `buffer_get_items` |
+| **json** | `buffer_transform`, `buffer_get_items` |
 | **xhtml** | `buffer_get_structure`, `buffer_get_element`, `buffer_validate_xhtml`, `confluence_draft_create` (with bufferId), `confluence_draft_save` |
 | **any** | `buffer_grep`, `buffer_list`, `buffer_clear`, `buffer_edit` (string mode) |
 
 **Error Messages**: When you use a tool with the wrong buffer type, you get a helpful error:
 ```
-buffer_pipeline requires json buffer, but got: xhtml.
+buffer_transform requires json buffer, but got: xhtml.
 For XHTML content, use buffer_edit or buffer_get_structure instead.
 ```
 
-**Key Principle**: If you have a JSON buffer (from Jira/Tempo search), use JSON-aware tools (`buffer_pipeline`, `buffer_get_items`). If you have an XHTML buffer (from Confluence), use XHTML-aware tools (`buffer_get_structure`, `buffer_edit` with element IDs).
+**Key Principle**: If you have a JSON buffer (from Jira/Tempo search), use JSON-aware tools (`buffer_transform`, `buffer_get_items`). If you have an XHTML buffer (from Confluence), use XHTML-aware tools (`buffer_get_structure`, `buffer_edit` with element IDs).
 
 ### Large Dataset Patterns
 
 **Simple table (no AI analysis):**
-Use `buffer_pipeline` - generates complete table in ONE tool call:
+Use `buffer_transform` - generates complete table in ONE tool call:
 ```typescript
 jira_search_issues({ jql: "project=PROJ" })  // → bufferId (500+ items)
-buffer_pipeline({ bufferId, pipeline: { output: { type: "xhtml_table", ... } } })  // → complete table!
+buffer_transform({ inputs: { issues: bufferId }, code: "return toTable(issues, { columns: [...] })" })  // → complete table!
 ```
 
 **Table with AI-enhanced columns (complexity, impact):**
@@ -2661,14 +2800,14 @@ buffer_validate_xhtml({
 **Automatic Validation:**
 XHTML content is automatically validated before Confluence writes (`confluence_draft_create`, `confluence_draft_save`).
 
-### JSON Pipeline Workflows
+### JSON Transform Workflows
 
-Use `buffer_pipeline` for efficient server-side data transformation. This eliminates the need to iterate through items in the LLM context.
+Use `buffer_transform` for efficient server-side data transformation. This eliminates the need to iterate through items in the LLM context.
 
 **Workflow - Search to Table (98% token reduction):**
 ```
 1. jira_search_issues(jql) → bufferId with JSON array
-2. buffer_pipeline(bufferId, pipeline) → bufferId with XHTML/CSV/Markdown
+2. buffer_transform(inputs, code) → bufferId with XHTML table
 3. Use result directly or insert into Confluence page
 ```
 
@@ -2679,29 +2818,27 @@ jira_search_issues({ jql: "project = PROJ AND type = Bug" })
 // → { bufferId: "buf_issues", structure: { itemCount: 150 } }
 
 // 2. Transform to table with one call (NOT iterating 150 items!)
-buffer_pipeline({
-  bufferId: "buf_issues",
-  pipeline: {
-    filter: [{ field: "status.name", operator: "ne", value: "Done" }],
-    sort: [{ field: "priority.name", direction: "asc" }],
-    format: [
-      { condition: { field: "priority.name", operator: "eq", value: "High" },
-        style: { color: "#dc3545", bold: true } }
-    ],
-    output: {
-      type: "xhtml_table",
-      table: {
-        title: "Open Bugs",
-        columns: [
-          { field: "key", header: "Issue", link: { type: "jira" } },
-          { field: "summary", header: "Summary" },
-          { field: "priority.name", header: "Priority" }
-        ]
-      }
-    }
-  }
+buffer_transform({
+  inputs: { issues: "buf_issues" },
+  code: `
+    const open = issues.filter(i => i.status?.name !== 'Done');
+    open.sort((a, b) => (a.priority?.id || 0) - (b.priority?.id || 0));
+
+    return toTable(open, {
+      title: 'Open Bugs',
+      columns: [
+        { field: 'key', header: 'Issue', link: { type: 'jira' } },
+        { field: 'summary', header: 'Summary' },
+        { field: 'priority.name', header: 'Priority' }
+      ],
+      format: [
+        { condition: { field: 'priority.name', operator: 'eq', value: 'High' },
+          style: { color: '#dc3545', bold: true } }
+      ]
+    });
+  `
 })
-// → { bufferId: "buf_table", outputItems: 45, preview: "<table>..." }
+// → { bufferId: "buf_table", contentType: "xhtml" }
 
 // 3. Insert into Confluence page
 confluence_edit("DOCS/Bug Report")
@@ -2715,41 +2852,39 @@ confluence_draft_create({ pageId: "123", bufferId: "buf_page" })
 **Workflow - Statistics Dashboard:**
 ```typescript
 // Group issues by assignee with counts
-buffer_pipeline({
-  bufferId: "buf_issues",
-  pipeline: {
-    filter: [{ field: "status.name", operator: "ne", value: "Done" }],
-    groupBy: {
-      field: "assignee.displayName",
-      aggregations: [
-        { function: "count", as: "total" },
-        { function: "list", field: "key", as: "issues" }
+buffer_transform({
+  inputs: { issues: "buf_issues" },
+  code: `
+    const open = issues.filter(i => i.status?.name !== 'Done');
+    const byAssignee = groupBy(open, 'assignee.displayName');
+
+    const stats = Object.entries(byAssignee).map(([name, items]) => ({
+      assignee: name || 'Unassigned',
+      total: items.length,
+      issues: items.map(i => i.key).join(', ')
+    }));
+    stats.sort((a, b) => b.total - a.total);
+
+    return toTable(stats, {
+      title: 'Work Distribution',
+      columns: [
+        { field: 'assignee', header: 'Assignee' },
+        { field: 'total', header: 'Open Issues', align: 'right' },
+        { field: 'issues', header: 'Issue Keys' }
       ]
-    },
-    sort: [{ field: "total", direction: "desc" }],
-    output: {
-      type: "xhtml_table",
-      table: {
-        title: "Work Distribution",
-        columns: [
-          { field: "displayName", header: "Assignee" },
-          { field: "total", header: "Open Issues" },
-          { field: "issues", header: "Issue Keys" }
-        ]
-      }
-    }
-  }
+    });
+  `
 })
 ```
 
-**When to Use `buffer_pipeline`:**
+**When to Use `buffer_transform`:**
 - Generating tables/lists for Confluence from Jira/Tempo data
 - Creating CSV/Markdown exports
 - Aggregating statistics (count by status, sum time by project, etc.)
 - Filtering and sorting large result sets server-side
 - Any data transformation that doesn't require LLM reasoning
 
-**When NOT to Use `buffer_pipeline`:**
+**When NOT to Use `buffer_transform`:**
 - When you need to read and understand each item's content
 - When decisions require LLM judgment (e.g., categorizing by sentiment)
 - When output format depends on item content analysis