No user-submitted related servers found.
Scored across 13 tools
Each tool maps to a distinct resource+action (search, get, create, update, comment, transition, attachment lifecycle), and the descriptions explicitly disambiguate the risky pairs like get_issue vs get_comments and update_issue vs transition_issue. Minor overlap remains: jira_get_issue already emits attachment metadata and partial comments, so an agent could plausibly skip jira_list_attachments or misuse get_issue for full discussions, but the docs steer correctly.
Every tool follows the same jira_<verb>_<noun> snake_case pattern (search_issues, get_issue, create_issue, add_comment, list_attachments, upload_attachment, cleanup_attachments). No camelCase or verb-style deviations; read vs write intent is further flagged in descriptions.
13 tools is squarely in the well-scoped range for a Jira integration and each one earns its place: the attachment trio (upload/download/cleanup) plus comment paging reflect real operational needs rather than bloat. Nothing appears redundant or filler.
Core issue lifecycle (search, get, create, update, comment, transition) and attachment handling are covered, but jira_create_issue demands an exact project key and issue type name while no tool lists projects, issue types, or creatable field metadata, which will cause trial-and-error failures. There is also no issue delete, no comment edit/delete, no issue-link or worklog operations, and no assignable-user lookup beyond get_current_user.