Skip to main content
Glama
dynstat

Figma Dash MCP Server

by dynstat

create_vector

Create vector nodes from SVG path strings to draw curves, waves, bezier shapes, custom icons, or area charts in Figma.

Instructions

Create a vector node from an SVG path string. This is the ONLY way to draw
curves, waves, bezier shapes, custom icons, or area charts in Figma.

pathData: SVG path commands (M, L, C, Q, A, Z, etc.)

── Wave / area chart recipe ───────────────────────────────────────────────
Closed path (ends with Z) gets fill — use for area-under-curve charts:
  pathData = "M 0,120 C 40,60 80,140 130,80 C 180,20 230,100 290,50
              L 290,160 L 0,160 Z"
  gradient = {"angle":180, "stops":[
    {"color":"#8B5CF6","position":0,"opacity":0.9},
    {"color":"#1C1E2A","position":1,"opacity":0}
  ]}
  shadow = {"color":"#7C3AED","x":0,"y":0,"blur":24,"spread":0,"opacity":0.7}

Open path (no Z) with noFill=True + stroke — use for line charts:
  pathData = "M 0,80 C 50,20 100,120 150,60 C 200,10 250,80 300,40"
  noFill = True
  stroke = "#8B5CF6"
  strokeWidth = 3

── Custom icon / shape ────────────────────────────────────────────────────
Any SVG path from Figma's pen tool or icon libraries works directly.

windingRule: 'NONZERO' (default) | 'EVENODD'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
nameNoVector
widthNo
heightNo
noFillNo
shadowNo
strokeNo
opacityNo
gradientNo
hexColorNo#FFFFFF
pathDataNoM 0 0 L 100 0
fillOpacityNo
strokeWidthNo
windingRuleNoNONZERO
strokeOpacityNo
Behavior4/5

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

With no annotations, the description carries full burden; it explains closed-path fill behavior vs open-path stroke/noFill, gives example gradient and shadow object structures, and mentions windingRule options. It does not disclose return value or coordinate details, but the core behaviors are well covered.

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?

Well-organized with clear section headers for wave/area chart and custom icon recipes, front-loaded with the core purpose. Despite length, each line provides actionable examples and earning its place; there's no fluff.

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?

For a 16-param tool with no annotations and no output schema, the description covers the main use cases and key behaviors effectively. It omits return value expectations and some param semantics (width/height auto-sizing), but the rich recipes and concrete examples are sufficient for an agent to invoke the tool correctly in common scenarios.

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 has 0% description coverage for 16 params, so the description must add meaning; it explains pathData syntax, windingRule values, and demonstrates noFill, stroke, strokeWidth, gradient, and shadow through concrete recipes. Many parameters (x, y, opacity, fillOpacity) are not directly explained but they are self-evident from names/defaults; the key vector-specific parameters are covered.

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?

Description states it creates a vector node from an SVG path string, with precise scope ('only way to draw curves, waves, bezier shapes, custom icons, or area charts'), clearly distinguishing from sibling line/rectangle/ellipse tools.

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?

Provides explicit use cases and recipes (closed path with Z for area-under-curve, open path with noFill+stroke for line charts), and names the tool as the only way for curved/bezier shapes. Does not explicitly mention exclusions like using create_line for straight paths, but the 'only way' framing gives adequate 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/dynstat/figma-dash-mcp'

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