Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_box_shadow_generator

Read-onlyIdempotent

Compose multi-layer CSS box-shadow declarations with per-layer offset, blur, spread, color, opacity, and inset settings. Includes HTML preview and CSS, SCSS, Tailwind snippets.

Instructions

CSS Box Shadow Generator. Compose one or more CSS box-shadow layers from per-layer offset, blur, spread, color, opacity, and inset settings, then return the combined box-shadow declaration plus a ready-to-paste HTML preview and CSS, inline, SCSS, and Tailwind usage snippets. Layers are joined in order into a single comma-separated declaration; per-layer opacity below 1 is folded into the color as rgba. Use webdev_border_radius_generator instead for rounded corners, webdev_css_gradient_generator for gradient backgrounds, and webdev_css_filter_generator for blur and brightness filter effects. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the box-shadow CSS string, the rendered preview HTML, the echoed layers, the layer count, and keyed usage examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shadowsYesOne or more shadow layers, joined left-to-right into one box-shadow declaration. At least one layer is required (empty returns HTTP 400).
previewSettingsNoOptional sizing and colors for the generated preview HTML only; does not affect the CSS declaration.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cssNoThe combined box-shadow CSS declaration joining all layers, ready to paste into a stylesheet.
previewHtmlNoSelf-contained HTML snippet rendering the shadow on a sample element.
usageExamplesNoKeyed copy-ready snippets (css, inline, sass, tailwind); each value has title and code strings.
shadowsNoThe echoed shadow layers after normalization.
shadowCountNoNumber of shadow layers in the declaration.
Behavior5/5

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

Beyond annotations, it adds local execution, rate limits, and opacity folding behavior. No contradiction with readOnlyHint/ idempotentHint.

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?

Two sentences, front-loaded purpose, efficient and complete without extra words.

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?

Mentions all key return elements and usage snippets. Output schema exists but description still provides context. No missing critical info.

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. Description adds value by summarizing parameters and explaining layer joining and opacity handling, earning a 4.

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 generates CSS box shadows from layers, with output details like combined declaration and usage snippets. It explicitly distinguishes from siblings by naming alternatives for related tasks.

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?

Directly specifies when to use alternatives: 'use webdev_border_radius_generator... for rounded corners' etc. Also states context: runs locally, read-only, rate-limited.

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