No user-submitted related servers found.
Scored across 2 tools
The two tools serve distinct purposes: one is a generic authenticated GET for any Jira or Confluence path, while the other is specifically a Jira JQL search. Although there is some overlap in that the GET could be used for search, the specific search tool is clearly targeted at JQL queries, making confusion unlikely.
The naming is inconsistent: one tool uses the 'atlassian_' prefix while the other uses 'jira_', and the verbs 'get' and 'search' do not follow a clear pattern. With only two tools, the lack of a unified convention is noticeable and could confuse agents expecting a consistent prefix.
Two tools is borderline thin for a server covering Atlassian's broad API surface, but it is not extreme enough to warrant a 1 or 2. The count is on the low end, feeling somewhat sparse but not entirely unreasonable for a focused read-only utility.
The server only offers read-only operations: a generic GET and a Jira search. It lacks write capabilities, Confluence-specific search, and any other common Atlassian operations, making it significantly incomplete for a platform with such a wide API. Agents would frequently hit dead ends when needing update or create functionality.