Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

webdev_javascript_beautifier

Read-onlyIdempotent

Pretty-print minified or messy JavaScript with configurable indentation, brace style, and spacing. Makes JS code readable without external services.

Instructions

JavaScript Beautifier. Pretty-print and re-indent minified or messy JavaScript with configurable indent (spaces or tabs), brace style, parenthesis spacing, and newline preservation. Use it to make JS readable; use webdev_js_minifier for the reverse (shrink for production), and webdev_code_formatter when you also need HTML/CSS in one pass. Runs locally on the code you provide: read-only, non-destructive, offline, contacts no external service, and is rate-limited. Returns the formatted code, token-count stats, and heuristic syntax warnings (it does not transpile or fully validate).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe JavaScript source to beautify (also accepted as "input").
optionsNoFormatting options. Omit for defaults.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formattedCodeNoThe beautified, re-indented JavaScript.
statsNoToken counts derived from the formatted code.
validationErrorsNoHeuristic syntax warnings (missing semicolons, unmatched quotes/braces); empty when none.

Schema Changelog

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

  1. Changed24 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / code / description
      Added value: +"The JavaScript source to beautify (also accepted as \"input\")."
    • addedInput schema / properties / code / examples
      Added value: +[
+  "function f(){return 1;}"
+]
    • addedInput schema / properties / options / additionalProperties
      Added value: +false
    • addedInput schema / properties / options / description
      Added value: +"Formatting options. Omit for defaults."
    • addedInput schema / properties / options / properties / braceStyle / default
      Added value: +"collapse"
    • addedInput schema / properties / options / properties / braceStyle / description
      Added value: +"Brace placement: collapse keeps the open brace on the same line; expand moves it to its own line."
    • addedInput schema / properties / options / properties / braceStyle / enum
      Added value: +[
+  "collapse",
+  "expand",
+  "end-expand"
+]
    • addedInput schema / properties / options / properties / indentSize / default
      Added value: +4
    • addedInput schema / properties / options / properties / indentSize / description
      Added value: +"Spaces per indent level (ignored when indentType is \"tab\")."
    • addedInput schema / properties / options / properties / indentSize / minimum
      Added value: +1
    • addedInput schema / properties / options / properties / indentType / default
      Added value: +"space"
    • addedInput schema / properties / options / properties / indentType / description
      Added value: +"Indent with spaces or a tab character."
    • addedInput schema / properties / options / properties / indentType / enum
      Added value: +[
+  "space",
+  "tab"
+]
    • addedInput schema / properties / options / properties / jslintHappy
      Added value: +{
+  "default": false,
+  "description": "Apply JSLint-friendly spacing conventions.",
+  "type": "boolean"
+}
    • addedInput schema / properties / options / properties / maxLineWidth / default
      Added value: +80
    • addedInput schema / properties / options / properties / maxLineWidth / description
      Added value: +"Target maximum line width hint."
    • addedInput schema / properties / options / properties / maxLineWidth / minimum
      Added value: +0
    • addedInput schema / properties / options / properties / preserveNewlines / default
      Added value: +true
    • addedInput schema / properties / options / properties / preserveNewlines / description
      Added value: +"Keep existing blank lines between statements."
    • addedInput schema / properties / options / properties / spaceInParen
      Added value: +{
+  "default": false,
+  "description": "Add spaces inside parentheses.",
+  "type": "boolean"
+}
    • removedInput schema / properties / options / required
      Removed value: -[
-  "indentType",
-  "indentSize",
-  "preserveNewlines",
-  "braceStyle",
-  "maxLineWidth"
-]
    • changedInput schema / required
      Previous value: -[
-  "code",
-  "options"
-]New value: +[
+  "code"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "formattedCode": {
+      "description": "The beautified, re-indented JavaScript.",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Token counts derived from the formatted code.",
+      "properties": {
+        "comments": {
+          "description": "Line and block comments counted.",
+          "type": "integer"
+        },
+        "functions": {
+          "description": "Named function declarations counted.",
+          "type": "integer"
+        },
+        "keywords": {
+          "description": "Reserved-word keyword occurrences counted.",
+          "type": "integer"
+        },
+        "operators": {
+          "description": "Operator occurrences counted.",
+          "type": "integer"
+        },
+        "strings": {
+          "description": "String literals counted.",
+          "type": "integer"
+        },
+        "variables": {
+          "description": "var/let/const declarations counted.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "validationErrors": {
+      "description": "Heuristic syntax warnings (missing semicolons, unmatched quotes/braces); empty when none.",
+      "items": {
+        "properties": {
+          "column": {
+            "description": "1-based column of the issue.",
+            "type": "integer"
+          },
+          "line": {
+            "description": "1-based line number of the issue.",
+            "type": "integer"
+          },
+          "message": {
+            "description": "Human-readable warning text.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds critical behavioral details: runs locally, read-only, non-destructive, offline, no external service, rate-limited, and returns formatted code with stats and syntax warnings. It also clarifies it does not transpile or fully validate, which is valuable beyond annotations.

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 two sentences long. The first sentence states the core purpose and key features; the second covers usage guidance, behavioral transparency, and output. Every sentence adds value, and critical information is front-loaded.

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 that an output schema exists, the description does not need to detail return values. It covers purpose, usage, behavioral traits, and output summary (formatted code, stats, warnings). The parameter schema is comprehensive, and the description complements it well. No obvious gaps.

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 coverage is 100%, so the baseline is 3. The description mentions configurable options (indent, brace style, etc.) but does not add meaning beyond what the input schema already provides (each option has a description and examples in the schema). No additional parameter guidance is given.

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 it is a JavaScript beautifier that pretty-prints and re-indents minified or messy JavaScript. It explicitly distinguishes from siblings webdev_js_minifier (reverse operation) and webdev_code_formatter (HTML/CSS in one pass), fulfilling the specific verb+resource+scope requirement.

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 when to use the tool ('use it to make JS readable') and names alternatives for other scenarios ('use webdev_js_minifier for the reverse... and webdev_code_formatter when you also need HTML/CSS in one pass'). This provides clear selection guidance.

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

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