Skip to main content
Glama
TranQui004

signalint

by TranQui004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_issue_detail

Read-onlyIdempotent

Retrieve full issue details for a specific cluster or issue from the latest check_project or check_files results. Supply exactly one ID.

Instructions

Returns the full issue list for either one cluster ID or one issue ID from the most recent check_project or check_files call. Read-only; no files are written or modified. Supply exactly one of clusterId or issueId — supplying both or neither returns an argument error. If the referenced cluster or issue no longer exists in the latest results (e.g., after re-running a check), returns a status: "stale" response instead of an error; call check_project or check_files again to refresh.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkIdNo
issueIdNo
clusterIdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
issuesNo
statusNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / properties / checkId
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / issues / items / properties / engine / enum
      Previous value: -[
-  "oxlint",
-  "tsc",
-  "biome"
-]New value: +[
+  "oxlint",
+  "tsc",
+  "biome",
+  "eslint"
+]
  2. Changed1 schema field changedv0.3.7
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "issues": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "clusterId": {
+            "type": "string"
+          },
+          "col": {
+            "type": "integer"
+          },
+          "engine": {
+            "enum": [
+              "oxlint",
+              "tsc",
+              "biome"
+            ],
+            "type": "string"
+          },
+          "file": {
+            "type": "string"
+          },
+          "fixable": {
+            "type": "boolean"
+          },
+          "issueId": {
+            "type": "string"
+          },
+          "line": {
+            "type": "integer"
+          },
+          "message": {
+            "type": "string"
+          },
+          "rule": {
+            "type": "string"
+          },
+          "severity": {
+            "enum": [
+              "error",
+              "warning"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "issueId",
+          "file",
+          "line",
+          "col",
+          "engine",
+          "rule",
+          "severity",
+          "message",
+          "fixable"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "stale",
+        "error"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observedv0.3.3

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only declare readOnly/idempotent/non-destructive), the description discloses non-obvious behavior: an argument error when both or neither ID is given, and a status: "stale" response instead of an error when the entity no longer exists after a re-run. This is exactly the kind of failure-mode detail annotations cannot carry.

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

Conciseness5/5

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

Three sentences, front-loaded with the core action, then constraints, then edge-case behavior. No filler; the brief redundancy about read-only is minor.

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

Completeness5/5

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

With an output schema present, return-value structure need not be explained, yet the description still flags the stale status shape. Combined with the parameter constraint and staleness recovery path, an agent has everything needed to call this correctly.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It clarifies the semantics of clusterId and issueId well (exactly-one-of, error otherwise), but the third parameter, checkId, is never mentioned in either the schema or the description, leaving a real gap.

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?

States a specific verb (returns) and resource (full issue list for one cluster ID or one issue ID), and explicitly ties the result to the most recent check_project or check_files call, which separates it from those siblings. An agent can distinguish it from check_project/check_files without opening a schema.

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?

Explicitly names the prerequisite context (must follow a check_project/check_files call), the constraint that exactly one of clusterId or issueId must be supplied, and the recovery action (call check_project or check_files again) when a stale response is returned.

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

Deploy Server

Other Tools