Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_smart_component

Create design-intelligent components with auto-layout, proper padding, and sizing using built-in design defaults.

Instructions

Create a design-intelligent component with proper auto-layout, padding, and sizing. Uses component intelligence defaults.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>"
    },
    "name": "create_smart_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoColor mode (default: dark)
typeYesComponent type: button, input, card, avatar, badge, chip, switch, checkbox, radio, toast, tooltip, modal, dropdown, tabs, table, progress, skeleton, divider
labelNoText label for the component
variantNoVariant: default, sm, lg, icon, compact, spacious, pill, thin
parentIdNoParent node ID
brandColorNoBrand/accent color hex

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It says the tool creates a component with auto-layout, padding, and sizing, but it does not disclose side effects, selection requirements, created node behavior, or return value. 'Uses component intelligence defaults' is too vague to be concrete.

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 brief and front-loaded with the main action. The phrase 'Uses component intelligence defaults' is somewhat vague but does not bloat the description; overall it is skimmable and efficient.

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?

This is a creation tool with six parameters, no annotations, and no output schema, yet the description omits what the tool returns, what 'smart' defaults actually do, and how it relates to sibling creation tools. An agent can guess the intent but lacks enough context to invoke it confidently.

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 coverage is 100%, so the baseline is 3 even though the description adds no parameter-specific meaning. The mention of auto-layout, padding, and sizing describes outcomes, not parameter semantics, and no parameter is clarified beyond what the schema already provides.

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 states a specific action and resource: create a component, plus design-relevant outcomes like auto-layout, padding, and sizing. However, terms like 'design-intelligent' and 'component intelligence defaults' are vague, and it does not explicitly differentiate this from the sibling create_component.

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 about when to use this tool versus alternatives such as create_component, create_component_set, or create_frame. The only implied signal is the 'smart' adjective, which is not a reliable selection criterion.

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