Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Design Generate Component

delimit_design_generate_component

Create a new React/Next.js component skeleton with TypeScript props and Tailwind CSS support. Scaffolds a .tsx file to jumpstart component development.

Instructions

Generate a React/Next.js component skeleton with Tailwind support.

When to use: to scaffold a new component (.tsx) with props interface and Tailwind class structure. When NOT to use: to generate stories for an existing component (use delimit_story_generate) or extract design tokens (delimit_design_extract_tokens).

Sibling contrast: delimit_story_generate adds stories to a component; this creates the component itself.

Side effects: writes a new component file (.tsx) under output_path or components//.tsx via backends.ui_bridge.design_generate_component. Detects Tailwind config inside project_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathNoOutput file path. Default = components/<Name>/<Name>.tsx.
project_pathNoProject root for Tailwind detection.
figma_node_idNoOptional Figma node ID (reserved for future use).
component_nameYesComponent name (PascalCase). Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.7.9
    • changedInput schema / properties / component_name / description
      Previous value: -"Component name (PascalCase)."New value: +"Component name (PascalCase). Required."
    • changedInput schema / properties / output_path / description
      Previous value: -"Output file path. Defaults to components/<Name>/<Name>.tsx."New value: +"Output file path. Default = components/<Name>/<Name>.tsx."
  2. Changed4 schema fields changedv4.5.5
    • addedInput schema / properties / component_name / description
      Added value: +"Component name (PascalCase)."
    • addedInput schema / properties / figma_node_id / description
      Added value: +"Optional Figma node ID (reserved for future use)."
    • addedInput schema / properties / output_path / description
      Added value: +"Output file path. Defaults to components/<Name>/<Name>.tsx."
    • addedInput schema / properties / project_path / description
      Added value: +"Project root for Tailwind detection."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=false; the description adds meaningful side-effect detail by stating it writes a new .tsx file to a specific location via a named backend and detects Tailwind config. This clarifies the mutation behavior beyond what the annotations alone convey.

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?

The description is well-structured with labeled sections, front-loads the core purpose, and every sentence serves a distinct function: purpose, usage, exclusions, sibling contrast, and side effects. There is no filler or redundant elaboration.

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

Completeness5/5

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

The tool has an output schema, full parameter coverage, annotations, and a description that covers purpose, usage boundaries, alternatives, and side effects. Nothing essential for correct invocation is missing.

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 schema already documents all four parameters. The description mostly restates output_path and project_path behavior already present in the schema, adding little new parameter-level meaning beyond the implementation detail of the backend call.

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?

The description opens with a specific verb and resource: 'Generate a React/Next.js component skeleton with Tailwind support.' It also differentiates from siblings by explicitly naming delimit_story_generate and delimit_design_extract_tokens, so an agent can disambiguate without inspecting other schemas.

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

Usage Guidelines5/5

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

The 'When to use' and 'When NOT to use' sections are explicit and actionable, naming the exact alternative tools for the excluded cases. The sibling contrast reinforces the routing decision, so no inference is required.

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