No user-submitted related servers found.
Scored across 2 tools
The two tools have overlapping purposes, as both fetch Linear issues, with the second tool adding comments. An agent could easily misselect between them when only basic issue details are needed, since the descriptions don't clearly differentiate when to use each beyond the comment inclusion. This creates ambiguity in tool selection for common workflows.
Both tools follow a consistent naming pattern with the prefix 'linear_get_issue' and descriptive suffixes ('', '_with_comments'), using snake_case uniformly. The naming is predictable and clearly indicates the domain and action, making it easy for agents to understand the tool set's structure.
With only 2 tools, this server feels severely under-scoped for managing Linear issues, a domain that typically requires CRUD operations like create, update, delete, search, and list. The limited tool count suggests incomplete coverage, making it difficult for agents to perform basic tasks beyond fetching issues.
The tool surface is severely incomplete for a Linear issues server, lacking essential operations such as creating, updating, deleting, listing, or searching issues. Agents will encounter dead ends when trying to perform common workflows, as the tools only support fetching issue details with or without comments, leaving major gaps in functionality.