Nexus Catalyst

Query Linear (read-only)

integration_query

Read-onlyIdempotent

Read-only Linear queries: fetch issues, projects, teams, labels, statuses, users and comments. This tool NEVER creates or modifies anything — use integration_mutate for that.

Actions: get_linear_projects, get_linear_issue, search_linear_issues, get_linear_teams, list_linear_labels, list_linear_statuses, list_linear_users, list_linear_comments, get_linear_comment_detail, get_linear_project_detail, list_linear_project_labels, get_linear_team_detail, get_project_context.

Pass workspace to select the Linear workspace when more than one is connected.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	The action to perform.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Per-action payload. Deliberately an open object: the action list is derived at runtime and each action has its own shape.
`error`	No	Present when the call did not succeed. An object carries `type` and `message` (and often a `timestamp`); Utils.formatError bodies set it to `true` with the reason in the top-level `message`.
`message`	No
`success`	No
`timestamp`	No	Unix epoch (milliseconds on most rows, seconds on legacy rows) or an ISO-8601 string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Envelope shared by every Linear action: `success`, a human-readable `message`, and `data` whose shape depends on the action (e.g. `{ issue }` for get_linear_issue, `{ issues, total }` for search_linear_issues, `{ disambiguation_required, available_workspaces }` when a workspace must be named).",
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "Per-action payload. Deliberately an open object: the action list is derived at runtime and each action has its own shape.",
+      "type": "object"
+    },
+    "error": {
+      "description": "Present when the call did not succeed. An object carries `type` and `message` (and often a `timestamp`); Utils.formatError bodies set it to `true` with the reason in the top-level `message`.",
+      "type": [
+        "object",
+        "boolean",
+        "string"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "timestamp": {
+      "description": "Unix epoch (milliseconds on most rows, seconds on legacy rows) or an ISO-8601 string.",
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false; the description reinforces this safety profile with the explicit 'NEVER creates or modifies anything'. It adds value beyond annotations by explaining the workspace selection behavior and the breadth of read-only actions available.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with its core purpose and safety guarantee, followed by the action list and workspace guidance. The action list is lengthy but necessary for a router-style tool; there is minor redundancy with the annotations but no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers overall scope, safety, and workspace selection, and the output schema exists to explain return values. However, each of the 13 actions is only named, not explained; the agent may struggle to know the required arguments or semantics of less obvious actions like get_project_context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only describes the action parameter generically, but the description adds meaning by listing all valid action values and explaining the workspace parameter's purpose. This compensates for the schema's minimal parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as performing read-only Linear queries, enumerating the resources it can fetch (issues, projects, teams, labels, statuses, users, comments). It explicitly contrasts itself with integration_mutate, making its scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states that this tool should not be used for creation or modification, directing the agent to integration_mutate instead. It also gives concrete guidance on passing workspace when multiple Linear workspaces are connected.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nexus Catalyst tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?