Skip to main content
Glama
zesun33
by zesun33

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_GDS_RUNTIMENoExecution runtime for tools. Set to 'host' to force host binaries instead of container (Podman) execution.podman

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
gds_infoA

Reads GDSII/OASIS layout metadata headlessly (cells, top cells, bounding boxes, per-layer shape counts). Pure introspection, no PDK needed. Use when you need to know what is inside a layout file.

gds_stream_outA

Streams a DEF layout to GDSII via headless KLayout using Nangate45 LEFs (abstract cell footprints; full transistor GDS needs the PDK). Use to produce DRC input or handoff previews, not tapeout signoff.

drc_klayoutA

Runs KLayout batch DRC on a GDS file. Default is a generated generic width/space smoke deck over the layout's own layers (geometry sanity, not foundry signoff). Pass deck_file for a real PDK rule deck. Does not do LVS; use lvs_netgen for netlist comparison.

lvs_netgenA

Compares two SPICE netlists with Netgen batch LVS and reports match/mismatch with net/device counts. Compares netlists only; use extract_magic to derive a layout netlist first. Does not do DRC.

extract_magicA

Extracts a SPICE netlist from layout with Magic batch mode (ext2spice lvs). Runs on generic technology: correct flow plumbing, but device-accurate extraction needs a PDK tech file.

gds_toolchain_infoA

Returns active container/host runtime and versions of KLayout, Magic, and Netgen.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/zesun33/mcp-gds'

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