Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_sidebar_layout

Build a sidebar and main content layout in Figma with adjustable widths and brand accent, ensuring proper proportions for UI designs.

Instructions

Create a sidebar + main content layout with proper proportions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_sidebar_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentIdNoParent node
brandColorNoAccent color
totalWidthNoTotal width (default: 1440)
sidebarWidthNoSidebar width (default: 260)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the mutation act 'create' without explaining where the layout is inserted, whether a parent is required, whether existing content is affected, or what nodes are actually generated. This is a significant gap for a mutation tool.

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?

A single ten-word sentence that front-loads the core action with no padding. The phrase 'with proper proportions' is somewhat vague, but brevity is otherwise well-handled.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and four optional parameters, an agent cannot tell what the tool returns, where the layout is created, or how the parameters shape the result. For a creation tool with zero structured safety signals, the description is too thin to support correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline of 3 applies. The description adds no parameter-specific meaning; 'proper proportions' loosely relates to totalWidth and sidebarWidth but does not clarify their relationship or acceptable values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific action ('Create') and resource ('sidebar + main content layout'), which distinguishes it from sibling layout creators such as create_nav_bar, create_header, and create_footer. It misses a 5 because 'proper proportions' is subjective and the expected output structure is never specified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to choose this tool over the many sibling layout/component creators, and no exclusions, prerequisites, or selection requirements are mentioned. An agent is left to infer the appropriate context entirely.

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