Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

sheet_add_paths

Append circuit paths to an existing power or control sheet by defining supplies, devices, terminals, labels, and feed continuations for electrical schematic drawings.

Instructions

Append current paths to an existing power/control sheet.

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": {
      "sheet_id": "<sheet_id>",
      "paths": "<paths>"
    },
    "name": "sheet_add_paths"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
sheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is known without the description. The description adds no behavioural context beyond that — it does not say the sheet is modified in place, that repeated calls append duplicates (non-idempotent), or what constraints apply to the target sheet.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with no filler, which is structurally clean. However its brevity comes at the cost of under-specification rather than genuine efficiency — there is nothing front-loaded about prerequisites or effect.

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, and the nested schema documents path fields well. But for a mutating append operation on an existing sheet, missing prerequisites and the non-idempotent append behaviour leave an agent without enough to call it confidently.

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?

Top-level schema description coverage is 0%: neither sheet_id nor paths is explained in the description. The nested $defs do carry rich field-level descriptions, but the description itself adds nothing about the required identifier format or the expected structure of the paths array, so it fails to compensate for the coverage gap it owns.

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 pairs a specific verb ('Append') with a specific resource ('paths') and names the target ('an existing power/control sheet'), so an agent knows this writes circuit paths onto an already-created sheet rather than creating one. It does not distinguish itself from siblings like sheet_add, and the phrase 'current paths' is slightly ambiguous, but the operation is recognisable.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over sheet_add or sheet_update, and no prerequisites are stated (e.g. the sheet must already exist, device tags must exist in the project, per the nested schema). The agent must infer all routing conditions.

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