Skip to main content
Glama
pzfreo

build123d-mcp

by pzfreo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

install_skill

Install a build123d workflow skill into your project so AI agents can follow step-by-step modeling, editing, or repair instructions; choose the target environment (Claude, Cursor, etc.) for automatic setup.

Instructions

Copy a b123d workflow skill into the current project.

Writes the appropriate config file for the requested agent so the
step-by-step workflow is available in future sessions.

skill: which workflow to install (default "modeling")
  - drawing   → DEPRECATED; still installs, but drawing generation has moved to
                draftwright, which publishes its own skill (#465)
  - modeling  → build 3D parts/assemblies (incl. from technical drawings)
  - edit      → modify existing build123d code and verify geometry deltas
  - repair    → repair a solid that fails the validity gate
target: one of "claude" (default), "agents-md", "cursor", "windsurf"
  - claude     → .claude/skills/<skill-dir>/SKILL.md  (Claude Code)
  - agents-md  → AGENTS.md  (Codex CLI, Antigravity, GitHub Copilot, Cline)
  - cursor     → .cursor/rules/<skill-dir>.mdc
  - windsurf   → .windsurfrules
force: overwrite existing installation (default False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNo
skillNomodeling
targetNoclaude

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.90
    • changedInput schema / properties / skill / default
      Previous value: -"drawing"New value: +"modeling"
  2. Changed1 schema field changedv0.3.49
    • addedInput schema / properties / skill
      Added value: +{
+  "default": "drawing",
+  "title": "Skill",
+  "type": "string"
+}
  3. Addedv0.3.34

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only indicate the operation is neither read-only nor destructive, so the description carries the burden. It goes beyond that by disclosing that files are written, listing exact destination paths per target, and showing that 'force: overwrite existing installation' controls destructive behavior. It also flags a deprecated skill variant. This is rich, honest behavioral context.

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 opening sentence states the core action, then the description breaks into tight bullet lists for skill and target with one-line definitions. The force parameter is handled in a single clear line. No filler or repetition — every sentence earns its place.

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?

For a tool with three parameters, multiple target paths, deprecated variants, and an overwrite flag, the description covers the action, all parameter semantics, file destinations, and deprecation note. Since an output schema exists, return values need not be described. Minor details like failure behavior without force are not essential for correct invocation.

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

Parameters5/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 fully compensate. It does: each parameter is documented with its default, allowed values, and effect — skill meanings, target agent paths, and force overwrite behavior. All three parameters are meaningfully explained beyond the bare schema definitions.

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 uses a specific verb ('Copy') and resource ('b123d workflow skill'), and elaborates on the concrete effect ('Writes the appropriate config file ... so the step-by-step workflow is available in future sessions'). It enumerates the skill and target options, which makes it unmistakably distinct from any sibling tool like workflow_hints.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool — installing a workflow skill for a specific agent — and details valid values for skill and target. It does not explicitly compare against sibling tools or state when not to use it, though the deprecated 'drawing' note hints at an alternative. This is clear context without exclusions, so a 4 is appropriate.

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