Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_sass_compiler

Read-onlyIdempotent

Compile SCSS or SASS source code into plain CSS. Resolve variables, nesting, mixins, and partials with selectable output styles and optional inline source maps.

Instructions

SCSS / SASS to CSS Compiler. Compile SCSS or indented-SASS source into plain CSS, resolving variables, nesting, mixins, and partials, with a choice of output styles (expanded, compressed, compact, nested) and optional inline source maps. Use this to turn a preprocessor stylesheet into deliverable CSS; use webdev_css_minifier instead when the input is already plain CSS you only want shrunk, or webdev_code_formatter to pretty-print CSS/HTML/JS. The server runs the Dart Sass CLI on the source you submit and returns the compiled CSS; remote @import and load-path lookups are disabled, so it reads no files off the host and contacts no external service. Read-only and non-destructive, rate-limited to 30 requests per minute for anonymous callers. Returns the compiled CSS, the echoed source, an optional source map, and size statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sassYesSCSS or SASS source code to compile. Must not be blank; an empty value is rejected.
syntaxNoSource syntax: scss for brace-and-semicolon SCSS, sass for the indented SASS syntax. Sets the temp file extension passed to the compiler.scss
outputStyleNoCSS formatting style forwarded to Dart Sass via the style flag. expanded is human-readable; compressed is minified.expanded
sourceMapNoWhen true, generate a source map and return its JSON in the sourceMap field.
includePathsNoAccepted and echoed for compatibility but ignored by the compiler (load paths are disabled for security, so remote or host @import lookups never run).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalNoThe submitted SCSS/SASS source, echoed back.
compiledNoThe compiled CSS output.
syntaxNoThe source syntax used (scss or sass).
outputStyleNoThe output style applied (expanded, compressed, compact, or nested).
sourceMapNoSource map JSON when sourceMap was requested and produced, otherwise null.
hasSourceMapNoWhether a source map is present in this response.
originalSizeNoCharacter length of the original source.
compiledSizeNoCharacter length of the compiled CSS.
compressionRatioNoSize change as a percentage of the original length.
errorNoPresent only on failure (HTTP 400/500): a cleaned compilation error message.
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds details: 'Read-only and non-destructive, rate-limited to 30 requests per minute for anonymous callers' and explains that the server runs Dart Sass without external file access, enhancing transparency 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 concise, fitting in 6 sentences without redundancy. It front-loads purpose, then provides usage guidance, implementation details, and return values. Every sentence adds value, making it efficient and well-structured.

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 (multiple parameters, output schema, annotations), the description covers all necessary aspects: purpose, alternatives, behavioral constraints, rate limits, and return fields (compiled CSS, source, source map, statistics). It is complete and no gaps are evident.

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 'includePaths' parameter is accepted but ignored for security, and outlines the effect of 'sourceMap' and 'outputStyle' options. This extra context justifies a score above baseline.

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 'SCSS / SASS to CSS Compiler' and lists key features like resolving variables, nesting, mixins, partials, and output styles. It explicitly distinguishes from siblings webdev_css_minifier and webdev_code_formatter, making the purpose unambiguous.

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 provides explicit when-to-use guidance: 'Use this to turn a preprocessor stylesheet into deliverable CSS; use webdev_css_minifier instead when the input is already plain CSS you only want shrunk, or webdev_code_formatter to pretty-print CSS/HTML/JS.' It also notes that remote @imports are disabled, giving clear context for appropriate use.

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