Skip to main content
Glama

design_initialize

Creates a project DESIGN.md from a chosen inspiration profile only when the file is missing, preventing overwrites of existing design documentation.

Instructions

Create a project DESIGN.md from an inspiration profile, only if absent. Never overwrites.

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": {
      "project_path": "<project_path>",
      "profile": "<profile>"
    },
    "name": "design_initialize"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-safe profile is partly covered. The description adds genuinely useful context beyond that — the create-if-absent guard and "Never overwrites" — but it does not say what happens on a second call (silent skip, error, or differing response), which matters given idempotentHint=false despite the create-if-absent semantics.

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?

Two short sentences, zero filler, with the core action front-loaded and the safety constraint immediately after. Nothing could be removed without losing information.

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

Completeness3/5

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

For a two-parameter write tool with no output schema, the description covers the action and the collision case, which are the essentials. It still leaves the agent guessing what the generated DESIGN.md contains, what each profile produces, and what the caller receives when the file already exists.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and it largely does not. "Profile" is gestured at as "an inspiration profile" but the enum values (linear, stripe, vercel, sap) are never explained as design-system inspirations, and project_path is left entirely undefined as to whether it is a directory, a repo root, or where DESIGN.md lands.

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 verb and artifact ("Create a project DESIGN.md") plus the source of its content ("from an inspiration profile"), which is concrete and distinguishable from read-oriented siblings like design_read or design_library_read. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

"only if absent" gives a clear precondition under which the tool acts and implies it will no-op or fail on an existing file. However, it offers no guidance about alternatives or sequencing, such as checking with design_read or design_audit first, so usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.