Skip to main content
Glama
guardianer9-debug

CST Studio Orchestrator MCP

cst_pcb_via_fence

Generate rows of vias along a path to create isolation barriers or Substrate Integrated Waveguides (SIW) in PCB designs.

Instructions

Create a row (or multiple rows) of vias along a path for isolation or Substrate Integrated Waveguide (SIW) construction. Generates an array of cylinders from start to end point with specified spacing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesBase name for the via fence
rowsNoNumber of parallel rows (1-3)
x_endYesX coordinate of the fence end in mm
y_endYesY coordinate of the fence end in mm
x_startYesX coordinate of the fence start in mm
y_startYesY coordinate of the fence start in mm
componentNoCST component namePCB
row_offset_mmNoLateral offset between rows for staggering in mm
via_spacing_mmYesCenter-to-center spacing between vias in mm
pad_diameter_mmYesVia pad diameter in mm
via_diameter_mmYesVia drill diameter in mm
Behavior3/5

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

With no annotations, the description carries full burden. It states it generates cylinders along a path, but lacks details on side effects, prerequisites, error handling, or impact on existing geometry. Basic behavior is covered but not deeply.

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

Conciseness4/5

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

The description is two sentences, short and front-loaded. Some redundancy between sentences (both mention arrays of vias), but overall efficient.

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?

Given 11 parameters and no output schema, the description provides basic purpose and method but lacks usage guidance, behavioral constraints, and output details. Adequate for simple usage but incomplete for novice users.

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 coverage is 100%, so baseline is 3. The description adds context about multiple rows and staggering, which are already in schema descriptions. No significant extra meaning beyond schema.

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 the tool creates a row of vias for isolation or SIW construction, with specific verb and resource. It distinguishes from sibling tools like cst_pcb_create_via which creates single vias, and other PCB geometry tools.

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 mentions use cases (isolation, SIW) but does not explicitly state when to prefer this over alternatives or provide exclusion criteria. No direct comparison with sibling tools is given.

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/guardianer9-debug/cst-studio-orchestrator-mcp'

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