Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Story Generate

delimit_story_generate

Scaffold a .stories.tsx file for a React/TSX component, generating per-variant stories without installing Storybook. Writes the file alongside the component for component-first authoring.

Instructions

Generate a .stories.tsx file for a UI component (no Storybook required).

When to use: to scaffold per-variant stories for a React/TSX component without installing the full Storybook toolchain. When NOT to use: for accessibility checks (use delimit_story_accessibility) or component scaffolding from scratch (delimit_design_generate_component).

Sibling contrast: delimit_design_generate_component creates the component; this generates its stories file. Together they form a component-first authoring path.

Side effects: writes a new .stories.tsx file next to the component. Coerces variants from a comma string to a list via _coerce_list_arg.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variantsNoVariants to generate (e.g. "Default,WithChildren"). Default = ["Default", "WithChildren"].
story_nameNoCustom story name. Default = component name.
component_pathYesPath to the component (.tsx) file. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.7.9
    • changedInput schema / properties / component_path / description
      Previous value: -"Path to the component file."New value: +"Path to the component (.tsx) file. Required."
    • changedInput schema / properties / story_name / description
      Previous value: -"Custom story name. Defaults to component name."New value: +"Custom story name. Default = component name."
    • changedInput schema / properties / variants / description
      Previous value: -"Variants to generate. Defaults to [Default, WithChildren]."New value: +"Variants to generate (e.g. \"Default,WithChildren\"). Default = [\"Default\", \"WithChildren\"]."
  2. Changed4 schema fields changedv4.5.5
    • addedInput schema / properties / component_path / description
      Added value: +"Path to the component file."
    • addedInput schema / properties / story_name / description
      Added value: +"Custom story name. Defaults to component name."
    • changedInput schema / properties / variants / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / variants / description
      Added value: +"Variants to generate. Defaults to [Default, WithChildren]."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only indicate non-read-only and non-destructive. The description adds valuable side-effect disclosure: it writes a new .stories.tsx file next to the component and coerces variants via _coerce_list_arg. It could also state what happens if the target file already exists, but the provided behavior is still solid.

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-organized with clear sections: purpose, when/how to use, sibling contrast, and side effects. Every sentence contributes useful information without unnecessary repetition.

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?

Covers purpose, usage boundaries, side effects, and variant coercion. An output schema exists, so return-value documentation is not required. The only minor gap is whether an existing .stories.tsx file is overwritten, but overall the description is sufficiently complete for invocation.

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 coverage is 100%, so the baseline is 3. The description adds extra meaning by explaining that variants can be supplied as a comma string and are coerced to a list, which is not evident from the schema alone.

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 states a specific verb and resource: 'Generate a .stories.tsx file for a UI component.' It also clarifies the Storybook-free context and contrasts with delimit_design_generate_component, so an agent can distinguish it from siblings.

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?

Provides explicit 'When to use' and 'When NOT to use' guidance, naming alternative tools (delimit_story_accessibility and delimit_design_generate_component). This leaves no ambiguity about routing.

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