Skip to main content
Glama
vuluu2k

WebCake Landing MCP

by vuluu2k

layout

Read-only

Computes exact on-canvas coordinates for elements in center, row, grid, or stack layouts, handling both desktop and mobile breakpoints automatically. Drop the results into your responsive styles.

Instructions

Computes EXACT on-canvas coordinates (top/left/width/height) for a group of elements, for BOTH breakpoints, following the guide's layout math — so you NEVER hand-compute left/top (the #1 source of off-center defects) or write a script to do it. Drop the returned boxes straight into each element's responsive..styles (results are in the same order you passed items). Four modes: 'center' (one box centered on the canvas); 'row' (N boxes in a horizontally-centered row on desktop that STACK into a single mobile column — feature cards / stats / logo strip); 'grid' (N uniform cells in cols columns, block centered; stacks on mobile); 'stack' (a vertical list down the shared content column on both breakpoints). Honours the page-margin axis (content column 80..880 desktop / 20..400 mobile by default). Pure math — no env, no network. notes flags off-canvas / over-wide inputs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapNoHorizontal gap between row/grid items (px). Default 24.
topNoDesktop start y inside the section (px). Default 0.
colsNoGrid columns. Default min(itemCount, 3).
modeYesLayout pattern. center=one box; row=horizontal row (stacks on mobile); grid=cols×rows (stacks on mobile); stack=vertical list.
alignNoHorizontal alignment of the block within the canvas. Default center.
countNoUniform shortcut: number of identical boxes (use with itemWidth/itemHeight).
itemsNoExplicit per-item sizes in order (row/stack may vary sizes). Provide this OR count+itemWidth+itemHeight.
rowGapNoVertical gap between grid rows / stacked items (px). Default = gap.
itemWidthNoUniform item width (with count).
mobileTopNoMobile start y (px). Default = top.
itemHeightNoUniform item height (with count).
canvasMobileNoMobile canvas width. Default 420 (use 360 to match a narrow design).
marginMobileNoMobile page margin / content inset. Default 20.
canvasDesktopNoDesktop canvas width. Default 960 (use 1200 for wide pages).
marginDesktopNoDesktop page margin / content inset. Default 80.
mobileItemWidthNoStacked-mobile item width (row/grid). Default = mobile content width.
Behavior5/5

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

Annotations include readOnlyHint=true and openWorldHint=false. The description aligns by stating 'Pure math — no env, no network.' It adds behavioral details: honours page margins, returns results in same order, and flags off-canvas/over-wide inputs via 'notes'. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear hierarchy: purpose, modes, constraints. Each sentence contributes useful information. Slightly lengthy but justified given the complexity of the tool.

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?

Given 16 parameters, high schema coverage, and no output schema, the description explains the core functionality, input patterns, and constraints. It could address error handling or edge cases like overflow, but overall it is sufficiently complete for an AI agent to use the tool.

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 already covers 100% of parameters with descriptions. The description adds meaning by explaining mode behaviors (e.g., 'row stacks on mobile'), the relationship between 'count' and 'items', and default values, enriching comprehension beyond the schema.

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 explicitly states it computes exact on-canvas coordinates for both breakpoints, lists four distinct layout modes, and distinguishes from sibling tools by emphasizing its pure math nature. It clearly defines what the tool does.

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?

The description advises against hand-computing or writing scripts, implying when to use. It explains the four modes and their stacking behavior, providing context. However, it does not explicitly state scenarios where this tool would be inappropriate or suggest alternatives, leaving minor room for interpretation.

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/vuluu2k/webcake-landing-mcp'

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