Skip to main content
Glama
RFingAdam

drawio-engineering-mcp

by RFingAdam

create_emc_test_setup

Generate an EMC test setup diagram from standardized templates (CISPR 25, ISO 11452) with equipment layout, distances, and labels, then open it in draw.io for editing.

Instructions

Generates an EMC test setup cross-section diagram from a template and opens it in draw.io. Shows equipment layout with ground plane, EUT on table, antenna on mast, and test instruments.

Available templates: cispr25_re: CISPR 25 Radiated Emissions - semi-anechoic chamber, antenna 1m from EUT, 150 kHz - 2.5 GHz cispr25_ce: CISPR 25 Conducted Emissions - LISN on each power line, 150 kHz - 108 MHz iso11452_2_ri: ISO 11452-2 Radiated Immunity - absorber-lined enclosure, 200 MHz - 18 GHz iso11452_4_ci: ISO 11452-4 Conducted Immunity (BCI) - BCI clamp on harness, 1 MHz - 400 MHz

Each template includes standard equipment, distances, and cable connections. Equipment labels can be overridden. Distance annotations are shown by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateYesEMC test standard template to use
titleNoDiagram title (defaults to template name)
show_distancesNoShow distance annotations between equipment. Default: true
equipment_overridesNoOverride default equipment labels. Keys are equipment names (eut, antenna, spectrum_analyzer, signal_generator, power_amplifier, power_meter, lisn, bci_probe), values are custom label strings.
auto_openNoAutomatically open the diagram in draw.io. Set to false to return XML only. Default: true
Behavior4/5

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

With no annotations, the description discloses that the tool generates a diagram from a template, opens in draw.io by default, and supports label overrides and distance annotations. It does not mention side effects or permissions, but adequate for a creation tool.

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?

The description is well-structured with clear sections and bullet points for templates, providing comprehensive information without unnecessary verbosity.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers templates, parameters, and behavior well, but lacks explicit mention of the return value (e.g., XML string or URL) when auto_open is false.

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 100% per context signals. The description adds value by explaining each template's purpose and listing possible keys for equipment_overrides, going beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates an EMC test setup diagram and opens it in draw.io, distinguishing it from sibling tools like create_rf_block_diagram and create_pcb_stackup.

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 description provides a list of available templates and mentions overrides, but does not explicitly state when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RFingAdam/drawio-engineering-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server