@crypto512/jicon-mcp 2.0.0 → 2.1.1

package/PROMPT.md

@@ -1,214 +1,33 @@
 # Jicon MCP Agent Prompt
 
-You are an assistant with access to the Jicon MCP server for Jira, Confluence, and Tempo operations. Follow these protocols strictly.
+You are an assistant with access to the Jicon MCP server for Jira, Confluence, and Tempo operations.
 
----
+## Before ANY Operation: Call Help
 
-## MANDATORY: Read Help Before Acting
+**Always start by reading the help documentation:**
 
-**Before ANY jicon operation, you MUST read the relevant help documentation.**
-
-### Step 1: Initial Orientation
 ```
-help()  ← Call this FIRST to get workflow decision tree
+help()  ← Returns workflow decision tree and quick reference
 ```
 
-### Step 2: Topic-Specific Help (Required Before Domain Operations)
+Then use topic-specific help for your task:
 
-| Task | Required Help Call |
-|------|--------------------|
-| Search Jira issues | `help(topic="jql")` |
+| Task | Help Command |
+|------|--------------|
+| Search Jira | `help(topic="jql")` |
 | Search Confluence | `help(topic="cql")` |
 | Edit Confluence pages | `help(topic="buffers")` then `help(topic="storage")` |
-| Create PlantUML diagrams | `help(topic="plantuml")` |
-| Work with large content | `help(topic="buffers")` |
-
-**DO NOT proceed with operations until you have read the relevant help topic.**
-
----
-
-## PlantUML Protocol (STRICT)
-
-PlantUML operations require a specific workflow. Deviations cause errors.
-
-### Mandatory Workflow
-
-```
-1. plantuml_validate(code="@startuml\n...\n@enduml")
-   ↓
-   If errors → FIX and re-validate (see Error Handling below)
-   ↓
-2. buffer_edit(bufferId, after=ID, plantuml="@startuml\n...\n@enduml")
-   ↓
-3. confluence_draft_save(draftId, bufferId)
-```
-
-### Critical Rules
-
-1. **ALWAYS validate first** - Even for "simple" diagrams
-2. **Use `plantuml` parameter** - The `content` parameter REJECTS PlantUML macros
-3. **Include markers required** - Every diagram needs `@startuml` and `@enduml`
-4. **One diagram per operation** - Multiple diagrams = multiple operations or batch
-
-### PlantUML Error Handling
-
-When `plantuml_validate` returns errors:
-
-```json
-{
-  "valid": false,
-  "errors": [
-    {"line": 5, "column": 10, "message": "Syntax error", "suggestion": "..."}
-  ]
-}
-```
-
-**You MUST:**
-1. Read the error location (line, column)
-2. Read the suggestion if provided
-3. Fix the PlantUML code at that location
-4. Re-validate until `valid: true`
-
-**You MUST NOT:**
-- Skip the diagram
-- Insert unvalidated code
-- Tell the user "it doesn't work"
-
-### Service Unavailable
-
-If you receive "PlantUML service unavailable":
-
-```
-1. plantuml_status()  ← Check what's wrong
-2. Report the specific issue to user:
-   - Docker not running
-   - Container failed to start
-   - Container died
-3. Suggest: "Please ensure Docker is running and restart the session"
-```
-
----
-
-## Buffer & Element ID Editing
-
-Confluence content is edited via buffers using stable element IDs.
-
-### Workflow
-
-```
-1. Get content:
-   confluence_get_page(pageId) OR confluence_draft_create(spaceKey, title)
-   → Returns: bufferId, structure
-
-2. Structure shows element IDs:
-   [
-     {id: 1, type: "h1", text: "Title"},
-     {id: 2, type: "p", text: "Content..."},
-     {id: 3, type: "plantuml", text: "Diagram"}
-   ]
+| PlantUML diagrams | `help(topic="plantuml")` |
 
-3. Edit by ID:
-   buffer_edit(bufferId, after=1, content="<p>New paragraph</p>")
-   buffer_edit(bufferId, replace=3, plantuml="@startuml...@enduml")
-   buffer_edit(bufferId, remove=2)
-
-4. Save:
-   confluence_draft_save(draftId, bufferId)
-```
-
-### Batch Operations (Preferred for Multiple Edits)
-
-```
-buffer_edit(bufferId, operations=[
-  {after: 1, content: "<h2>Section</h2>"},
-  {after: 2, plantuml: "@startuml\nA -> B\n@enduml"},
-  {remove: 5}
-])
-```
-
-Benefits: Single parse, single validation, atomic execution.
-
----
-
-## ERROR HANDLING MANDATE
-
-### NEVER Skip Tasks Due to Errors
-
-When you encounter an error:
-
-1. **READ** the full error message (includes diagnostics)
-2. **ANALYZE** the cause using error details
-3. **FIX** the issue based on error guidance
-4. **RETRY** the operation
-5. **REPEAT** steps 1-4 up to 3 times
-
-**Only after 3 failed fix attempts** may you report being blocked.
-
-### Error Recovery Reference
-
-| Error Type | Recovery Action |
-|------------|-----------------|
-| PlantUML syntax error | Fix code at reported line/column, re-validate |
-| Element not found | Call `buffer_get_structure(bufferId)` to see valid IDs |
-| Buffer expired | Re-fetch content to get new bufferId |
-| XHTML parse error | Check `suggestedActions` in error, fix malformed XML |
-| Multiple occurrences | Use `replace_all=true` for string replacement |
-| Permission denied | Report to user - configuration issue |
-| Service unavailable | Call status tool, report specific issue |
-
-### XHTML Error Recovery
-
-When `confluence_draft_save` fails with XHTML error:
-
-```
-1. Error includes: errorLocation (element ID), suggestedActions
-2. buffer_get_element(bufferId, elementId)  ← Inspect problem element
-3. buffer_edit(bufferId, replace=elementId, content="<fixed XHTML>")
-4. Retry save
-```
-
----
-
-## Quick Reference
-
-### Help Topics
+## Available Topics
 
 | Topic | Content |
 |-------|---------|
 | (none) | Workflow decision tree, core patterns |
-| `jql` | Jira Query Language syntax, operators, examples |
-| `cql` | Confluence Query Language syntax, operators, examples |
-| `storage` | Confluence XHTML format, macros, layouts |
-| `plantuml` | PlantUML validation workflow, macro structure |
-| `buffers` | Element ID system, buffer operations, batch editing |
-
-### Common PlantUML Fixes
-
-| Error | Fix |
-|-------|-----|
-| Missing @startuml | Add `@startuml` at start |
-| Missing @enduml | Add `@enduml` at end |
-| Unexpected token | Check syntax at reported line |
-| Unknown entity | Verify class/actor/component name spelling |
-| C4 not recognized | Add `!include` for C4 library |
-
-### Buffer Operation Types
-
-| Operation | Parameters |
-|-----------|------------|
-| Insert after | `after=ID, content="..." OR plantuml="..."` |
-| Insert before | `before=ID, content="..." OR plantuml="..."` |
-| Replace | `replace=ID, content="..." OR plantuml="..."` |
-| Remove | `remove=ID` |
-| Append | `append=true, content="..." OR plantuml="..."` |
-
----
-
-## Core Principles
+| `jql` | Jira Query Language syntax |
+| `cql` | Confluence Query Language syntax |
+| `storage` | Confluence XHTML format |
+| `plantuml` | PlantUML validation workflow |
+| `buffers` | Element ID system, buffer operations |
 
-1. **Help-First**: Always read documentation before acting
-2. **Validate-First**: For PlantUML, validation is mandatory before insertion
-3. **Fix-Not-Skip**: Errors are problems to solve, not reasons to abandon tasks
-4. **ID-Based Editing**: Use element IDs for precise content manipulation
-5. **Batch When Possible**: Multiple edits should use operations array
-6. **Retry With Fixes**: Failed operations require analysis and correction, not abandonment
+The help system provides complete guidance for all operations. Read it before proceeding.

package/README.md

@@ -31,9 +31,11 @@ Once configured, just ask in natural language:
 
 ### Jira
 - *"Find all high-priority bugs assigned to me"*
+- *"What happened on project ACME this week?"* (Activity digest)
 - *"Create a task for implementing user authentication"*
 - *"Move PROJ-123 to Done and add a comment that it's deployed"*
 - *"Show me the current sprint's progress"*
+- *"Summarize recent discussions about authentication"* (Comment analysis)
 - *"Link PROJ-456 as blocking PROJ-789"*
 
 ### Confluence
@@ -136,7 +138,7 @@ All configuration is done through environment variables.
 | `JICON_PERMISSIONS_WHITELIST` | comma-separated | - | Tools to allow (custom mode) |
 | `JICON_PERMISSIONS_BLACKLIST` | comma-separated | - | Tools to deny (custom mode) |
 | `JICON_CONFLUENCE_WRITE_HOME` | `true`\|`false` | `false` | Restrict Confluence writes to personal space |
-| `JICON_DISABLE_DOCKER` | `true`\|`false` | `false` | Disable PlantUML/Docker features |
+| `JICON_PLANTUML_SERVER_URL` | string | - | PlantUML server URL (e.g., `http://localhost:8080`) |
 | `JICON_MAX_OUTPUT` | number | `16000` | Maximum output characters |
 
 **Note:** Tempo uses the same Jira credentials - no separate configuration needed.
@@ -207,34 +209,20 @@ This configuration allows:
 
 **Individual tools** (for blacklist): See [TOOL_LIST.md](TOOL_LIST.md) for all tool names
 
-### Docker Configuration
+### PlantUML Configuration
 
-PlantUML validation requires Docker. The container starts when MCP loads and does **not auto-restart** if it stops - you'll need to restart the MCP server.
+PlantUML validation requires an external PlantUML server. If not configured, PlantUML tools are disabled.
 
-**Disable Docker/PlantUML**:
+**Configure PlantUML server**:
 ```json
 {
   "env": {
-    "JICON_DISABLE_DOCKER": "true"
+    "JICON_PLANTUML_SERVER_URL": "http://localhost:8080"
   }
 }
 ```
 
-When disabled, PlantUML tools return clear errors instead of failing silently.
-
-### PlantUML Include Expansion
-
-C4-PlantUML, AWS icons, and Azure diagrams require `!include` directives. By default, Jicon expands these includes client-side before validation and sending to Confluence.
-
-**Whitelisted URLs:**
-- `https://raw.githubusercontent.com/plantuml-stdlib/` - C4, Azure, Kubernetes, etc.
-- `https://raw.githubusercontent.com/plantuml/` - Official PlantUML stdlib
-- `https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/` - AWS icons
-
-**Disable include expansion** (if you encounter issues):
-```json
-{ "plantumlInclude": false }
-```
+You can use the public PlantUML server (`http://www.plantuml.com/plantuml`) or run your own with Docker: `docker run -d -p 8080:8080 plantuml/plantuml-server:jetty`.
 
 ## Authentication
 
@@ -257,7 +245,7 @@ C4-PlantUML, AWS icons, and Azure diagrams require `!include` directives. By def
 - **Jira** Server/Data Center or Cloud with API access
 - **Confluence** (optional) Server/Data Center or Cloud
 - **Tempo** (optional) Timesheets plugin
-- **Docker** (optional) For PlantUML diagram validation
+- **PlantUML Server** (optional) External server for diagram validation
 
 ## API Limitations
 
@@ -290,15 +278,28 @@ This achieves "draft before publish" semantics within API constraints.
 
 ## Features
 
-### 71 Tools Across 3 Services
+### 75 Tools Across 3 Services
 
 | Service | Capabilities |
 |---------|--------------|
-| **Jira** (18 tools) | Search, create, update, transition issues; manage comments, links, watchers; access boards, sprints, worklogs |
+| **Jira** (22 tools) | Search, create, update, transition issues; manage comments, links, watchers; access boards, sprints, worklogs; **LLM-powered analysis** |
 | **Confluence** (21 tools) | Search, create, edit pages via drafts; manage spaces, comments, attachments; PlantUML diagrams; review workflow |
 | **Tempo** (12 tools) | Log time, view/update worklogs, team tracking, accounts |
 
-Plus utility tools for content buffering, time calculations, URL generation, and built-in help.
+Plus utility tools for content buffering, time calculations, URL generation, date resolution, and built-in help.
+
+### LLM-Powered Analysis Tools
+
+These **intelligent entry points** are designed for AI synthesis - they return pre-processed content directly to the LLM (not buffered) for analysis and insight generation:
+
+| Tool | Purpose |
+|------|---------|
+| **Activity Digest** | Fetches comments, status/priority/assignee changes across issues. Ask: *"What happened on project X this week?"* |
+| **Recent Comments** | Aggregates comments across multiple issues. Ask: *"Any blockers mentioned in recent discussions?"* |
+| **Changelog** | Tracks field changes across issues. Ask: *"What issues had priority escalations?"* |
+| **Analyze Epic** | Comprehensive Epic analysis: hierarchy breakdown, time metrics, velocity, linked Confluence pages, recent discussions. Ask: *"Analyze Epic PROJ-100 for progress and risks"* |
+
+These tools return **markdown formatted for LLM comprehension** with pre-computed summaries (counts, breakdowns), enabling the AI to focus on **insight and synthesis** rather than data extraction.
 
 ### Buffered Responses
 
@@ -329,7 +330,7 @@ This means the AI assistant **never directly modifies** existing pages - all cha
 
 ### PlantUML Diagrams
 
-Create and validate UML diagrams directly in Confluence pages. The PlantUML Docker container starts automatically when the MCP server loads (if Docker is available). If Docker is unavailable or the container stops, PlantUML tools return clear errors - restart the MCP server to retry. Use `"disableDocker": true` in config to skip PlantUML entirely.
+Create and validate UML diagrams directly in Confluence pages. Configure `JICON_PLANTUML_SERVER_URL` to enable diagram validation. If not configured, PlantUML tools return clear errors explaining how to enable them.
 
 ## Tool Reference
 

package/TOOL_LIST.md

@@ -5,14 +5,15 @@ This document provides a comprehensive reference of all available tools in the J
 
 ## Summary
 
-**Total Tools**: 70
-- **Jira Tools**: 18 (13 read + 5 write)
+**Total Tools**: 75
+- **Jira Tools**: 22 (17 read + 5 write)
 - **Confluence Tools**: 21 (13 read + 8 write)
 - **Tempo Tools**: 12 (9 read + 3 write)
 - **Buffer Tools**: 11
 - **Workload Tools**: 2
 - **URL Tools**: 2
 - **Jicon Help Tools**: 1
+- **Date Tools**: 1
 - **PlantUML Tools**: 3
 
 **Note**: All data-heavy tools (search, list, get) **always** return buffered responses with metadata for origin tracking:
@@ -138,7 +139,7 @@ When XHTML validation fails, the response includes element ID and suggested acti
 
 ---
 
-## Jira Tools (18)
+## Jira Tools (21)
 
 ### 1. jira_search_issues
 **Description**: Search for Jira issues using JQL. Auto-fetches all results (up to 5000).
@@ -389,6 +390,142 @@ When XHTML validation fails, the response includes element ID and suggested acti
 
 ---
 
+### 19. 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
+
+Fetches comments, status changes, priority changes, and assignee changes - formatted for LLM synthesis.
+
+| 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") |
+| includeComments | boolean | ✗ | Include comments (default: true) |
+| includeStatusChanges | boolean | ✗ | Include status changes (default: true) |
+| includePriorityChanges | boolean | ✗ | Include priority changes (default: true) |
+| includeAssigneeChanges | boolean | ✗ | Include assignee changes (default: true) |
+| maxActivities | number | ✗ | Maximum activities to return (default: 50) |
+| commentMaxLength | number | ✗ | Max length for comment text (default: 500) |
+
+**At least one scoping parameter required**: `projectKey`, `jql`, or `issueKeys`
+
+**Returns**: Markdown-formatted activity digest with pre-computed summary:
+```markdown
+# Activity Digest: Project ACME (Last 7 days)
+
+## ACME-123: Payment gateway integration
+- **status**: "In Progress" → "In Review" (Jan 28, by @john)
+**Comments (2)**:
+- @john (Jan 28 14:30): "Completed Stripe integration..."
+- @sarah (Jan 29 09:15): "Found edge case with refunds..."
+
+---
+## Summary
+- **Issues with activity**: 12
+- **Status changes**: 8 (3 to Done/Closed)
+- **Priority changes**: 2
+- **Comments**: 15
+```
+
+---
+
+### 20. 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
+
+| 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") |
+| authorKey | string | ✗ | Filter by comment author username |
+| maxComments | number | ✗ | Maximum comments to return (default: 30) |
+| includeContext | boolean | ✗ | Include issue summary/status (default: true) |
+
+**At least one scoping parameter required**: `projectKey`, `jql`, or `issueKeys`
+
+**Returns**: Markdown-formatted comments grouped by issue with summary statistics.
+
+---
+
+### 21. 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
+
+| 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") |
+| fields | string[] | ✗ | Fields to track (default: ["status", "priority", "assignee", "resolution"]) |
+| maxChanges | number | ✗ | Maximum changes to return (default: 50) |
+
+**At least one scoping parameter required**: `projectKey`, `jql`, or `issueKeys`
+
+**Returns**: Markdown-formatted changelog with field breakdown:
+```markdown
+# Changelog: Project ACME (Last 7 days)
+
+## ACME-123: Payment gateway integration
+- Jan 28 14:00: **status**: "In Progress" → "In Review" (by @john)
+- Jan 25 09:00: **assignee**: "Unassigned" → "@john" (by @lead)
+
+---
+**Total**: 12 changes across 6 issues
+**By field**: status (7), priority (3), assignee (2)
+```
+
+---
+
+### 22. 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
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| issueKey | string | ✓ | Epic or parent issue key (e.g., PROJ-123) |
+| includeComments | boolean | ✗ | Include recent comments (default: true) |
+| commentDays | number | ✗ | Days of comments to include (default: 14) |
+| maxComments | number | ✗ | Max comments per issue (default: 5) |
+
+**Returns**: Comprehensive markdown analysis including:
+- **Issue Hierarchy**: Breakdown by type (Epic, Story, Task, Sub-task) with completion percentages
+- **Time Metrics**: Time spent, original estimate, remaining, burn rate, overrun warnings
+- **Progress Indicators**: Completion rate, in-flight issues, projected total
+- **Architecture Context**: Components and labels across all issues
+- **Linked Resources**: Confluence pages, related issues
+- **Recent Discussions**: Comments from the last N days
+
+**Example output**:
+```markdown
+# Epic Analysis: PROJ-100
+**Payment Gateway Integration**
+
+## Issue Hierarchy
+
+| Type | Total | Done | In Progress | To Do | Completion |
+|------|-------|------|-------------|-------|------------|
+| Story | 5 | 3 | 1 | 1 | 60% |
+| Sub-task | 12 | 8 | 2 | 2 | 67% |
+| **TOTAL** | **17** | **11** | **3** | **3** | **65%** |
+
+## Time Metrics
+- **Time Spent**: 2w 3d
+- **Original Estimate**: 3w
+- **Remaining Estimate**: 1w 2d
+- **Burn Rate**: 77% of estimate consumed
+
+## Analysis Summary
+This Epic contains **17 issues** with **65% completion**.
+Currently **3 issues** are in progress.
+```
+
+---
+
 ## Confluence Tools (21)
 
 ### 1. confluence_search_content
@@ -1678,7 +1815,7 @@ buffer_get_structure({ bufferId: "buf_xxx" })
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
 | bufferId | string | ✓ | Buffer ID containing XHTML content |
-| validatePlantUml | boolean | ✗ | Validate PlantUML syntax via Docker service (default: true) |
+| validatePlantUml | boolean | ✗ | Validate PlantUML syntax via PlantUML server (default: true) |
 
 **Type Requirement**: Buffer must have `contentType: "xhtml"`. Returns error if buffer is JSON or plain text.
 
@@ -1687,11 +1824,11 @@ buffer_get_structure({ bufferId: "buf_xxx" })
 - Required attributes on Confluence elements (ac:name, ri:space-key, etc.)
 - Valid layout section types (single, two_equal, etc.)
 - Known macro names (warns for unknown macros)
-- PlantUML syntax (via Docker service, if running)
+- PlantUML syntax (via PlantUML server, if configured)
 
 **PlantUML validation**:
-- If Docker service is running, validates all PlantUML macros
-- If not running, adds warning (use `plantuml_validate` to start the service)
+- If PlantUML server is configured, validates all PlantUML macros
+- If not configured, adds warning (set `JICON_PLANTUML_SERVER_URL` to enable)
 
 **Response includes**: `valid`, `errorCount`, `warningCount`, `errors`, `warnings`
 
@@ -1804,12 +1941,13 @@ Unified help system for all Jicon workflows and syntax guides. Always available
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
-| topic | string | ✗ | Topic for detailed help: jql, cql, storage, plantuml, buffers |
+| topic | string | ✗ | Topic for detailed help: jql, cql, storage, plantuml, buffers, analysis |
 
 **Default (no topic)**: Compact workflow guide with decision trees showing:
 - Confluence workflows (create page, update page, draft workflow, search)
 - Jira workflows (search issues, create issue, worklogs)
 - Tempo workflows (log work, get worklogs)
+- LLM-powered analysis tools (activity digest, comments, changelog, epic analysis)
 - Buffer patterns for large responses and editing
 - Utility tools (fullurl, workload_convert)
 - Decision tree for when to call each topic
@@ -1823,6 +1961,7 @@ Unified help system for all Jicon workflows and syntax guides. Always available
 | `storage` | Confluence storage format + structure editing (element IDs) |
 | `plantuml` | PlantUML syntax for Confluence diagrams |
 | `buffers` | Buffer management and element ID editing guide |
+| `analysis` | LLM-powered analysis tools for AI synthesis |
 
 **Examples**:
 ```typescript
@@ -1831,20 +1970,73 @@ help(topic="jql")            // JQL syntax guide
 help(topic="storage")        // Basic Confluence formatting
 help(topic="plantuml")       // PlantUML diagram syntax
 help(topic="buffers")        // Buffer management guide
+help(topic="analysis")       // LLM analysis tools guide
+```
+
+**Tip**: Start with `help()` to understand the overall workflow. For AI analysis tasks (e.g., "What happened on project X?"), check `help(topic="analysis")`.
+
+---
+
+## Date Tools (1)
+
+Date resolution utility for pre-computing date ranges. Always available with any Jira, Confluence, or Tempo action.
+
+### 1. 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
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| expression | string | ✓ | Date expression (see below) |
+| businessDays | boolean | ✗ | Use business days (Mon-Fri) for weeks (default: true) |
+
+**Supported Expressions**:
+
+| Expression | Description |
+|------------|-------------|
+| `today` | Current day |
+| `yesterday` | Previous day |
+| `this_week` | Current week (Mon to today, business days by default) |
+| `last_week` | Previous full week |
+| `this_month` | Current month (1st to today) |
+| `last_month` | Previous full month |
+| `this_quarter` | Current quarter (Q start to today) |
+| `last_quarter` | Previous full quarter |
+| `last_7d`, `last_14d`, `last_30d`, `last_90d` | Last N days |
+| `ytd` | Year to date |
+| `Nd` (e.g., `5d`, `10d`) | Last N days |
+
+**Returns**:
+```json
+{
+  "dateFrom": "2026-01-27",
+  "dateTo": "2026-01-31",
+  "businessDays": 5,
+  "calendarDays": 5,
+  "description": "This week (Mon Jan 27 - Fri Jan 31, 2026)",
+  "expression": "this_week"
+}
+```
+
+**Examples**:
+```typescript
+date_resolve(expression="last_week")  // Get last week's date range
+date_resolve(expression="7d")         // Last 7 days
+date_resolve(expression="this_month") // Current month to date
 ```
 
-**Tip**: Start with `help()` to understand the overall workflow, then use specific topics for syntax details.
+**Tip**: Use the returned `dateFrom` and `dateTo` directly in Jira/Tempo queries.
 
 ---
 
 ## PlantUML Tools (3)
 
-Docker-based PlantUML validation and rendering. Requires Docker to be installed and running.
+PlantUML validation and rendering via external server. Configure with `JICON_PLANTUML_SERVER_URL` environment variable.
 
-**Docker Lifecycle**:
-- Container starts **at MCP server startup** (not lazily on first use)
-- Does **NOT auto-restart** if container stops - restart MCP server to retry
-- Use `"disableDocker": true` in `.jicon.json` to skip PlantUML entirely
+**Server Configuration**:
+- Set `JICON_PLANTUML_SERVER_URL` to your PlantUML server URL (e.g., `http://localhost:8080`)
+- If not set, PlantUML tools are disabled and return clear error messages
+- Public server: `http://www.plantuml.com/plantuml` (rate limited)
 
 **Stdlib Includes (C4, AWS, Azure):**
 ```
@@ -1896,20 +2088,19 @@ plantuml_render({
 ---
 
 ### 3. plantuml_status
-**Description**: Check PlantUML service status
-**Use Cases**: Verify Docker service is running, troubleshoot connection issues
+**Description**: Check PlantUML server status
+**Use Cases**: Verify PlantUML server is available, troubleshoot connection issues
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
 | (none) | | | |
 
-**Response includes**: `available`, `disabled`, `startupFailed`, `containerDied`, `error`, `containerId`, `port`, `baseUrl`, `message`
+**Response includes**: `available`, `disabled`, `serverDied`, `error`, `serverUrl`, `message`
 
 **Status States**:
-- `available: true` - Container running and healthy
-- `disabled: true` - Disabled via `disableDocker: true` config
-- `startupFailed: true` - Docker failed at MCP startup (check logs)
-- `containerDied: true` - Container stopped after startup (restart MCP)
+- `available: true` - Server is reachable and healthy
+- `disabled: true` - Not configured (`JICON_PLANTUML_SERVER_URL` not set)
+- `serverDied: true` - Server became unreachable after initial connection
 
 ---
 
@@ -2162,7 +2353,7 @@ buffer_validate_xhtml({
 - Required attributes on Confluence elements (ac:name, ri:space-key, etc.)
 - Valid layout section types
 - Known macro names (warnings for unknown macros)
-- PlantUML syntax (requires Docker - returns error if unavailable)
+- PlantUML syntax (requires PlantUML server - returns error if unavailable)
 
 **Automatic Validation:**
 XHTML content is automatically validated before Confluence writes (`confluence_draft_create`, `confluence_draft_save`).