Server has 12 tools across Jira and Confluence with basic structure, but critical gaps in schema visibility and parameter documentation. Tool names follow verb_noun convention (jira_search_issues, confluence_create_page), which is good. However, source code provided is incomplete, only utility functions and partial main.py shown, not actual tool definitions. Cannot verify input schemas, parameter descriptions, or output documentation for any tool. Descriptions appear to exist (inferred from tool names) but are not visible in provided code.

• Provide complete tool definitions (jira.py, confluence.py) showing input schemas, parameter types, descriptions, and output schemas. Current code snippet is incomplete.
• Add parameter descriptions for all inputs. Example: 'jql' param in jira_search_issues should document JQL syntax, max length, and common patterns.
• Implement pagination for search_issues and search_pages: add limit (1 - 100, default 20) and offset/cursor parameters; return total_count and next_cursor in response.
• Add dry-run or confirmation step for write operations. E.g., jira_create_issue could accept a 'confirm' boolean; if false, return a preview of what would be created.
• Document output schemas for all tools. Specify which fields are returned, their types, and which IDs/references are included for chaining (e.g., issue_id for downstream add_comment calls).

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry