Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

project_update

Update title-block fields or switch standards profiles (IEC, IEC legacy, NFPA) so electrical project documentation matches the required standard.

Instructions

Update title-block fields and/or switch the standards profile (iec / iec_legacy / nfpa).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
plantNo
authorNo
clientNo
companyNo
machineNo
profileNo
reviewerNo
revisionNo
descriptionNo
project_titleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds the profile enum values, which the schema omits entirely, but leaves key behavior unstated: whether omitted fields are left untouched, whether the whole title block is replaced, and whether switching profile rewrites existing text.

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 covering both capabilities with zero filler. The profile enumeration is placed inline where it is needed rather than deferred.

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

Completeness2/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, but for an 11-parameter mutation with zero schema descriptions the definition is thin. It should clarify which parameters map to which title-block slots and what happens to fields left null on a partial update.

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?

Eleven parameters at 0% schema coverage means the schema contributes no descriptions at all, so the description carries the full burden. It names the profile values but never maps the other ten fields (date, plant, author, client, company, machine, reviewer, revision, description, project_title) to title-block positions or explains their formats and null semantics.

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 concrete verb (update) and two concrete resources: title-block fields and the standards profile, with the allowed profile values spelled out (iec / iec_legacy / nfpa). It is distinguishable from project_create or sheet_update by naming title-block/profile scope, though it never explicitly contrasts with those siblings.

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?

Usage is only implied: 'update title-block fields and/or switch the standards profile' tells the agent the two supported operations, and 'and/or' signals they can be combined. There is no explicit when-to-use vs. when-not, no prerequisites, and no mention of the sibling tools (project_create, device_update) that might be confused with it.

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