Skip to main content
Glama
guardianer9-debug

CST Studio Orchestrator MCP

cst_pcb_cpw_transition

Create a tapered CPW-to-microstrip transition in CST Studio. Linearly tapers center conductor width and gap over the transition length for impedance matching.

Instructions

Create a coplanar waveguide (CPW) to microstrip transition in CST Studio. Generates a tapered geometry that linearly tapers the center conductor width and gap over the transition length. Calculates CPW and microstrip impedances.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the transition structure
layerYesLayer name (e.g. 'Top')
componentNoCST component namePCB
epsilon_rNoSubstrate relative permittivity
height_mmYesSubstrate height to reference plane in mm
cpw_gap_mmYesCPW gap width in mm
cpw_width_mmYesCPW center conductor width in mm
transition_typeNoType of transitioncpw_to_microstrip
microstrip_width_mmYesMicrostrip trace width at the end of the transition in mm
transition_length_mmYesLength of the tapered transition in mm
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It mentions generating a tapered geometry and calculating impedances, but does not disclose potential side effects, required permissions, or whether it modifies existing geometry or creates new objects.

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 three sentences long, front-loaded with the main action, followed by taper details and calculation. Every sentence adds value, no unnecessary words.

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?

Given the tool's complexity (10 parameters, transition design), the description covers the purpose and taper mechanism. It does not explain the output (no output schema) or the transition_type enum options, but it reasonably addresses the main behavior. Slightly more detail on output would improve completeness.

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?

The input schema has 100% coverage with descriptions for each parameter. The description adds value by explaining that the center conductor width and gap are linearly tapered, directly relating to parameters like cpw_width_mm, cpw_gap_mm, transition_length_mm, and microstrip_width_mm. It also mentions impedance calculation, adding domain context beyond the 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 CPW-to-microstrip transition with a tapered geometry, specifying the linear taper of center conductor width and gap over transition length, and mentions impedance calculation. It is distinct from siblings like cst_pcb_create_trace which creates generic traces.

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?

The description provides no guidance on when to use this tool versus alternatives such as cst_pcb_create_trace or cst_pcb_differential_pair. It does not mention prerequisites, complementary tools, or suitable scenarios.

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