Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

reports

Export BOM, wire, terminal, PLC I/O, and network lists to XLSX or CSV to prepare electrical project documentation.

Instructions

Export BOM, wire list, terminal list, PLC I/O list and network list to XLSX (+ CSV).

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": "reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the agent knows this writes something without destroying data. The description adds little beyond the format: it does not say where files land, whether an existing file is overwritten, or how many files are produced. With annotations carrying the safety profile, this is adequate but thin.

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 the verb and the full resource list first, formats second. No filler, no repetition of the tool name.

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?

The output schema exists, so return values need not be described. However, for a file-writing export tool the description omits the destination path, overwrite policy, and whether all five report types are always produced or selectable. Those gaps matter more than format enumeration, which is already covered.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, so the description carries the burden. The parenthetical '(+ CSV)' hints that the csv flag controls parallel CSV output alongside XLSX, but it never states that explicitly or explains the default=true behavior. It adds marginal meaning over the bare boolean.

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 names a specific verb (Export) and enumerates the exact artifacts produced: BOM, wire list, terminal list, PLC I/O list and network list, in XLSX/CSV formats. That is far more specific than a tautology. It stops short of explicitly contrasting with the *_list siblings that return the same data in-session rather than as files.

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 statement of when to call this versus the read-only list tools (network_list, plc_io_list, device_list) that expose similar data interactively. No prerequisites, no mention of whether a project must be open, and no exclusions are given. Usage is only inferable from the word 'Export'.

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