Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

project_open

Opens an existing project by its workspace code or full .elec.yaml path, letting you load electrical documentation data for viewing and editing.

Instructions

Open an existing project by code (from the workspace) or by the full path of its .elec.yaml.

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": {
      "code_or_path": "<code_or_path>"
    },
    "name": "project_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
code_or_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, so opening actually changes state, yet the description never says what changes (e.g., does it set an active/session project?) or what happens if a project is already open. It also says nothing about failure behavior for a bad code or path. With annotations present the bar is lower, but the non-read-only nature of "open" is counterintuitive and left unexplained.

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?

A single front-loaded sentence with zero padding; both identifier forms are stated compactly.

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 described, and the single parameter is well covered. What remains missing is state-change and error behavior for a non-read-only, non-idempotent operation on a session context.

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 0% and the parameter is a bare "code_or_path" string, so the description carries the burden — and it does, explaining that the value is either a workspace project code or the full path of an .elec.yaml file. This is exactly the meaning an agent could not infer from the schema alone.

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?

States a specific verb and resource ("Open an existing project") and clarifies the two accepted identifier forms. The word "existing" implicitly separates it from project_create, though no sibling is named explicitly.

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?

The word "existing" implies this is for projects already created, so a caller can infer it is not the creation path. However, there is no explicit when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as cadcraft_open.

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