OnlineCyberTools MCP (280+ filterable tools)

webdev_code_formatter

Read-onlyIdempotent

Format or minify HTML, CSS, or JavaScript code with configurable indentation and comment preservation. Select language and action, returns processed code with size and line statistics.

Instructions

HTML/CSS/JS Code Formatter and Minifier. Pretty-print or minify a single HTML, CSS, or JavaScript snippet using whitespace/brace indentation rules. Set language to pick the dialect and action to format (readable, indented) or minify (whitespace/comments stripped). This is the multi-language dispatcher: use webdev_css_beautifier or webdev_javascript_beautifier for those single languages, and webdev_sql_formatter, json_formatter, or webdev_xml_formatter for SQL/JSON/XML (not supported here). Heuristic whitespace formatter, not an AST validator, so JSX, template literals, and malformed input may need review. Runs locally via a Node bridge: read-only, non-destructive, contacts no external service, rate-limited (60 req/min anon). Returns the processed output plus size/line statistics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Source code to process (alias: input). Must be non-empty.
`language`	No	Source dialect. Unknown values fall back to html.	html
`action`	No	format = readable indentation; minify = strip whitespace (and comments unless preserved). Any value other than "minify" is treated as format.	format
`options`	No	Formatting/minifying options.

Output Schema

TableJSON Schema

Name	Required	Description
`input`	No	The original code, echoed back.
`output`	No	The formatted or minified result.
`language`	No	Language actually used (post-fallback).
`action`	No	Action actually applied.
`statistics`	No	Size and line metrics comparing input to output.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed22 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / action / default
```
Added value: +"format"
```

addedInput schema / properties / action / description

Added value: +"format = readable indentation; minify = strip whitespace (and comments unless preserved). Any value other than \"minify\" is treated as format."

addedInput schema / properties / action / enum

Added value: +[
+  "format",
+  "minify"
+]

addedInput schema / properties / code / description

Added value: +"Source code to process (alias: input). Must be non-empty."

addedInput schema / properties / code / examples

Added value: +[
+  "body{color:red;margin:0;}"
+]

addedInput schema / properties / language / default
```
Added value: +"html"
```

addedInput schema / properties / language / description

Added value: +"Source dialect. Unknown values fall back to html."

addedInput schema / properties / language / enum

Added value: +[
+  "html",
+  "css",
+  "javascript"
+]

addedInput schema / properties / options / additionalProperties
```
Added value: +false
```
addedInput schema / properties / options / description
```
Added value: +"Formatting/minifying options."
```
addedInput schema / properties / options / properties / indentSize / default
```
Added value: +"4"
```

addedInput schema / properties / options / properties / indentSize / description

Added value: +"Spaces per indent level (format only); the string \"tab\" uses a tab character."

addedInput schema / properties / options / properties / indentSize / examples
```
Added value: +[
+  "4",
+  "tab"
+]
```
changedInput schema / properties / options / properties / indentSize / type
```
Previous value: -"string"New value: +[
+  "string",
+  "integer"
+]
```
addedInput schema / properties / options / properties / maxLineLength / default
```
Added value: +100
```

addedInput schema / properties / options / properties / maxLineLength / description

Added value: +"Advisory max line length (accepted but does not hard-wrap output)."

addedInput schema / properties / options / properties / preserveComments / default
```
Added value: +true
```
addedInput schema / properties / options / properties / preserveComments / description
```
Added value: +"Keep comments when minifying. Ignored when action is format."
```

removedInput schema / properties / options / required

Removed value: -[
-  "indentSize",
-  "maxLineLength",
-  "preserveComments"
-]

changedInput schema / required

Previous value: -[
-  "code",
-  "language",
-  "action",
-  "options"
-]New value: +[
+  "code"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "action": {
+      "description": "Action actually applied.",
+      "enum": [
+        "format",
+        "minify"
+      ],
+      "type": "string"
+    },
+    "input": {
+      "description": "The original code, echoed back.",
+      "type": "string"
+    },
+    "language": {
+      "description": "Language actually used (post-fallback).",
+      "enum": [
+        "html",
+        "css",
+        "javascript"
+      ],
+      "type": "string"
+    },
+    "output": {
+      "description": "The formatted or minified result.",
+      "type": "string"
+    },
+    "statistics": {
+      "description": "Size and line metrics comparing input to output.",
+      "properties": {
+        "compressionRatio": {
+          "description": "Percent size reduction for minify; null when action is format.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "originalLines": {
+          "description": "Newline-split line count of the input.",
+          "type": "integer"
+        },
+        "originalSize": {
+          "description": "Input length in characters.",
+          "type": "integer"
+        },
+        "processedLines": {
+          "description": "Newline-split line count of the output.",
+          "type": "integer"
+        },
+        "processedSize": {
+          "description": "Output length in characters.",
+          "type": "integer"
+        },
+        "sizeDifference": {
+          "description": "processedSize minus originalSize (negative when smaller).",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (readOnly, non-destructive), description adds details about local execution via Node bridge, rate limiting (60 req/min anon), and output contents (size/line stats). No contradictions.

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 concise, front-loaded with key actions, and structured with clear sections: summary, usage guidance, limitations, and behavioral notes. Every sentence adds value.

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?

Given the tool's complexity (4 params, nested object, output schema), the description covers all essential aspects: purpose, usage, alternatives, limitations, behavior, and output. No gaps.

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 100%, so baseline is 3. The description adds value by explaining the meaning of 'format' vs 'minify' actions and the role of indentSize, but schema descriptions already cover parameters well.

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 states the tool formats and minifies HTML, CSS, or JavaScript code, and identifies it as a multi-language dispatcher. It differentiates from sibling tools like webdev_css_beautifier and webdev_javascript_beautifier.

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 tells when to use this tool versus alternatives (e.g., for single languages or SQL/JSON/XML). Also warns about limitations like JSX and malformed input, guiding appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server