Skip to main content
Glama
the-real-talk

the-real-talk

create_component

Creates an empty component inside a parent frame or the current page, letting you define its name, position, and dimensions during design system construction.

Instructions

Create an empty component in a parent (default: current page).

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_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNo
widthNo
heightNo
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only discloses that the result is empty and defaults to the current page. It says nothing about required permissions, what happens to the x/y/width/height values if omitted, whether an id or node is returned, or whether properties must be added afterward via add_component_property.

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 short sentence with the core action front-loaded and the default parent folded into a parenthetical. Nothing is wasted, though the extreme terseness leaves the tool under-explained rather than trimmed of fat.

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?

For a six-parameter mutation tool with no annotations and no output schema, one sentence is not enough. An agent cannot determine from this definition how geometry parameters behave, what the call returns, or what state the new component is in beyond being empty.

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 0% across six parameters, and the description only clarifies parentId's default. The meaning of x, y, width, and height (units, coordinate space, auto-sizing behavior) and how name is derived when omitted remain undocumented in both places.

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 clear verb and resource ("Create an empty component") and adds a scope detail about where it lands. The word "empty" helps distinguish it from create_component_instance, though no sibling is named explicitly.

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?

There is no guidance on when to use this versus convert_to_component, create_component_instance, or create_frame. The parent default is mentioned, but nothing tells the agent which situations call for this tool or what prerequisites exist.

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