Skip to main content
Glama
Sign In
Strudel MCP Server

Strudel MCP Server

by williamzujkowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

diagnostics

Inspect Strudel MCP server and browser state to troubleshoot caches, errors, performance, and memory using status, full, perf, memory, or errors levels.

Instructions

Inspect server and browser state. level=status returns a quick state snapshot (cache read, <15ms SLA), plus which config.json was read and any warnings from it. level=full returns detailed browser diagnostics including caches, errors, and performance. level=perf returns server-side timing metrics + top bottlenecks. level=memory returns process memory usage. level=errors returns captured console errors and warnings from Strudel. Default level=full preserves the pre-consolidation behaviour. Example: diagnostics({ level: "status" }) — millisecond-cheap. For screenshots use browser_window; for tool listings use the strudel://docs/tools resource.

Input Schema

NameRequiredDescriptionDefault
levelNoWhich diagnostic surface to read (default: full)
session_idNoOptional session ID (#108). Applies to level=status, full, errors. Ignored for perf/memory (server-wide metrics).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.0.0
    • addedInput schema / properties / level
      Added value: +{
+  "description": "Which diagnostic surface to read (default: full)",
+  "enum": [
+    "status",
+    "full",
+    "perf",
+    "memory",
+    "errors"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Optional session ID (#108). Applies to level=status, full, errors. Ignored for perf/memory (server-wide metrics).",
+  "type": "string"
+}
  2. Addedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses a <15ms SLA for status, that config.json provenance and warnings are surfaced, and that session_id is ignored for perf/memory because those are server-wide metrics. It stops short of stating that the tool is read-only and side-effect free, which has to be inferred from "Inspect".

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?

Front-loaded with the verb and the cheapest level first, then the heavier surfaces, then the redirects, then the example. Dense but nearly every clause carries information; the level enumeration is long but functional. Minor redundancy between the opening scope statement and the per-level list.

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

Completeness4/5

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

For a two-param, no-output-schema tool, the description adequately fills the return-value gap by naming what each level yields (snapshots, caches, errors, timing metrics, memory). Return shapes remain coarse, but that is acceptable for a diagnostics surface where the caller inspects the payload anyway.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning beyond the enum by explaining what each level actually returns and by scoping session_id's applicability (status/full/errors) versus perf/memory. That is semantic information the schema's terse "Which diagnostic surface to read" does not provide.

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 opens with a specific verb+resource pair ("Inspect server and browser state") and then enumerates all five level values with what each one returns, so an agent can distinguish this from siblings like session or browser_window without opening the schema. The scope (server-side vs browser-side surfaces) is made explicit per level.

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

Usage Guidelines4/5

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

It states the default (level=full preserves pre-consolidation behaviour) and gives an explicit example call for the cheap path, plus routes two adjacent needs elsewhere ("For screenshots use browser_window; for tool listings use the strudel://docs/tools resource"). It does not contrast against diagnostic-adjacent siblings like session or history, so the routing is useful but not exhaustive.

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