Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

project_create

Create a new electrical project, select an IEC or NFPA profile, and set it as the active .elec.yaml workspace project for immediate documentation work.

Instructions

Create a new electrical project and make it the active one.

profile: 'iec' (IEC 81346-2:2019 two-letter codes, vertical paths, A3), 'iec_legacy' (single-letter -K/-F/-Q codes) or 'nfpa' (NFPA 79 ladder, ANSI B). Standard potentials L1 L2 L3 N PE 24V 0V are pre-declared. The project is saved as .elec.yaml in the workspace (or in directory).

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_code": "<project_code>"
    },
    "name": "project_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
plantNo
authorNo
clientNo
companyNo
machineNo
profileNoiec
reviewerNo
revisionNoA
directoryNo
overwriteNo
descriptionNo
project_codeYes
project_titleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds useful behavior beyond that: the new project becomes active, standard potentials are pre-declared, profiles control drawing conventions, and the project is saved as <code>.elec.yaml in the workspace or directory. It does not explain overwrite conflict behavior or permission requirements.

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?

The description is front-loaded with the core action and then supplies relevant profile and save-location details. It is compact overall, though the profile parenthetical is dense and could be structured more cleanly.

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?

An output schema exists, so return values need not be explained. However, for a 13-parameter creation tool, the description omits important semantics such as overwrite behavior and most metadata fields, leaving the agent to rely on undocumented schema properties.

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% across 13 parameters, so the description must compensate. It explains the profile values and the directory/file-location behavior, but leaves overwrite, project_title, author, company, client, machine, revision, reviewer, plant, and description undocumented.

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 resource: create a new electrical project and make it active. This clearly distinguishes the operation from opening or listing projects, though it does not explicitly name project_open as the alternative for existing projects.

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?

"Create a new electrical project" implies the tool is for new projects, but there is no explicit when-to-use guidance versus project_open or project_list. The agent must infer that this is not for opening existing projects.

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