Skip to main content
Glama
AvYour

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check a design for defects

figma_check_layout
Read-only

Audit Figma frames for layout problems: overflowing or overlapping text, clipping, zero-size nodes, low contrast, and use of placeholder copy. Returns numbered findings with fixes.

Instructions

After each section and before calling anything done: a designer's last look, in numbers (figma_export_node shows the picture). Per node, with a number and fix: text overflowing, collapsed, overlapping or painted over; content clipped or sticking out; a fill child in a hug parent; stacked frames; placeholder copy ("Lorem ipsum", "Acme"); low contrast (WCAG); zero-size nodes, empty frames, default names; on a slide, content off it, bleeds, cut text. audit adds passes: tokens (raw values, with the variable to bind), names (duplicate components, variants), fonts (expectFonts flags others), board (FigJam rules), craft (finish: near-equal sizes, unshared edges, near-touches, lines through text, old-style figures, shape contrast, faint hairlines, a sunk block; safeArea, minTextSize), tells (the generated look, info only), handoff (share bound to variables or styles, detached instances). ok: true = no errors or warnings. Default: the selection, then the page (Slides: focused slide). Reads only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auditNoQA passes to add: tokens, names, fonts, board, craft (finish defects), tells (the generated look; info only), handoff (how much is bound to the system).
limitNoMax findings returned. Default 100.
nodeIdNoThe frame or section to check. Defaults to every selected node, then the page.
nodeIdsNoSeveral roots in one call, e.g. a batch of 3–5 slides. Not with nodeId.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
maxNodesNoStop after this many nodes. Default 3000.
safeAreaNo"x,y,width,height" in the root's coordinates (its top-left is 0,0), from the brief — no presets. Text, logos and CTAs outside it are flagged. Implies craft.
expectFontsNoFont families the design should use, e.g. ["Inter"]; implies the fonts audit.
minSeverityNoHide findings below this level. Default "info".
minTextSizeNoSmallest readable text in px of the frame: the device's floor × frame width ÷ device width, e.g. 28 or more on a 1080-wide story. Implies craft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint/destructiveHint already covering the safety profile, the description adds meaningful context: result semantics ('ok: true = no errors or warnings'), each audit pass behavior, that 'tells' is informational only, and that tokens pass returns the variable to bind. It also implies cost bounds via maxNodes defaults. It does not discuss pagination or performance limits beyond that.

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?

Front-loads the timing and purpose, then compresses defect classes and audit-pass semantics into a dense but scannable telegraphic style. Every sentence carries information, though the heavy semicolon/backtick packing makes it harder to parse than a cleanly structured list would be.

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?

With no output schema, the description carries the return burden and does so partially: it explains 'ok: true' and 'number and fix' per finding, default scope, and audit-pass additions. It covers enough for a correct invocation, though result shape details (severity fields, counts) are only implied.

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 the baseline is 3, but the description adds cross-parameter semantics the schema lacks: safeArea and minTextSize 'imply craft', expectFonts 'implies the fonts audit', and each audit enum value is explained with its output meaning (e.g. tells = info only). This goes beyond restating 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?

States a specific verb and resource (checks a Figma design/selection for layout defects) and enumerates the concrete defect classes it reports (overflow, overlap, clipping, placeholder copy, low contrast, zero-size nodes). It explicitly contrasts itself with the visual sibling figma_export_node and distinguishes itself from the surrounding mutation tools in the suite.

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?

Gives clear timing guidance ('after each section and before calling anything done') and names the alternative for the visual view (figma_export_node). It also states the default scope (selection, then page, or focused slide). It stops short of explicit when-not-to-use or exclusion conditions, but the context is unambiguous.

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

Deploy Server

Other Tools