Skip to main content
Glama
MarlonJD

web-debug-mcp

by MarlonJD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect Next.js runtime

web_next_inspect
Destructive

Compile a Next.js route or resolve a Server Action through the local development server to verify flow behavior and produce reproducible evidence.

Instructions

Compile one Next.js route or resolve one Server Action through the selected local Next development server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYes
inspectionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
errorNo
warningsYes
artifactsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • addedOutput schema / definitions / JsonValue
      Added value: +{
+  "allOf": [
+    {
+      "$ref": "#/definitions/__schema0"
+    }
+  ]
+}
    • changedOutput schema / definitions / __schema0 / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  },
-  {
-    "items": {
-      "$ref": "#/definitions/__schema0"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {
-      "$ref": "#/definitions/__schema0"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  },
+  {
+    "items": {
+      "allOf": [
+        {
+          "$ref": "#/definitions/__schema0"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": {
+      "allOf": [
+        {
+          "$ref": "#/definitions/__schema0"
+        }
+      ]
+    },
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  }
+]
    • changedOutput schema / properties / data / properties / result / anyOf
      Previous value: -[
-  {
-    "$ref": "#/definitions/__schema0"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/definitions/JsonValue"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed5 schema fields changedv0.7.0
    • addedOutput schema / properties / data / additionalProperties
      Added value: +false
    • removedOutput schema / properties / data / allOf
      Removed value: -[
-  {
-    "$ref": "#/definitions/__schema0"
-  }
-]
    • addedOutput schema / properties / data / properties
      Added value: +{
+  "detected": {
+    "const": true,
+    "type": "boolean"
+  },
+  "endpoint": {
+    "maxLength": 2560,
+    "type": "string"
+  },
+  "kind": {
+    "enum": [
+      "compileRoute",
+      "resolveServerAction"
+    ],
+    "type": "string"
+  },
+  "result": {
+    "anyOf": [
+      {
+        "$ref": "#/definitions/__schema0"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "warnings": {
+    "items": {
+      "maxLength": 500,
+      "type": "string"
+    },
+    "maxItems": 20,
+    "type": "array"
+  }
+}
    • addedOutput schema / properties / data / required
      Added value: +[
+  "detected",
+  "endpoint",
+  "kind",
+  "result",
+  "warnings"
+]
    • addedOutput schema / properties / data / type
      Added value: +"object"
  3. First observedv0.5.0-next.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already convey the tool is not read-only, is not idempotent, and is potentially destructive, so the description doesn't need to restate those traits. It adds useful context by scoping execution to a 'selected local Next development server' and to a single route/action, but it does not disclose what side effects compilation or server-action resolution might produce.

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?

The description is a single, well-structured sentence that front-loads the two distinct operations and scopes them to the dev server. There is no redundant phrasing or filler; every word contributes meaning.

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?

Given the presence of annotations and an output schema, the core call semantics are adequately covered. The main gaps are the lack of usage guidance versus sibling tools and the unresolved ambiguity around routeSpecifier versus path, which prevents the description from feeling fully complete for correct invocation.

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?

With 0% schema description coverage, the description partially compensates by explaining that sessionId refers to a selected local Next dev server and that inspection covers one of two modes. However, it does not clarify how 'path' and 'routeSpecifier' differ for compileRoute, nor what actionId should contain beyond a generic string.

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 uses specific verbs ('Compile', 'resolve') and names the exact resources: a Next.js route and a Server Action. It directly maps to the two variants in the schema (compileRoute and resolveServerAction), making the tool's function unmistakable even alongside its siblings.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives like web_debug_evaluate or web_repro_record. It explains what the tool does, but not the conditions that should lead an agent to select it or scenarios where it should not be used.

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