Skip to main content
Glama
ismailakdag

cst-studio-mcp

by ismailakdag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cst_configure_time_domain_solver

Configure the transient solver for broadband CST simulations by setting accuracy, excitation type, port, and impedance normalization for a single-run S-parameter and field calculation.

Instructions

Configure the time domain (transient) solver. This is CST's flagship solver for broadband simulations — it excites the structure with a pulse and computes S-parameters, fields, and farfield across the entire frequency range in a single run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accuracyNoAccuracy level in dB — solver stops when energy has decayed to this level (default -40)
max_time_stepsNoMaximum number of time steps; 0 means automatic (default 0)
excitation_typeNoExcitation signal shape (default Gaussian)Gaussian
fixed_impedanceNoReference impedance in ohms when normalization is enabled (default 50)
stimulation_portNoPort number used for excitation (default 1)
normalize_to_fixed_impedanceNoNormalize S-parameters to a fixed reference impedance (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses excitation method and outputs (S-params, fields, farfield) but does not mention prerequisites, potential issues, or side effects.

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?

Two concise sentences, front-loaded with purpose, no wasteful words. Second sentence adds valuable behavioral context.

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?

No output schema, but description covers main outputs. Lacks information on prerequisites (e.g., open project, defined ports) and typical usage flow. Adequate for a configure tool.

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?

All 6 parameters have descriptions in the input schema (100% coverage). The description does not add any additional meaning or usage context beyond what the schema already provides.

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?

Clearly states it configures the time domain solver and distinguishes it from frequency domain by describing broadband pulse excitation and single-run computation of S-parameters, fields, and farfield across the entire frequency range.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use for broadband simulations needing S-params/fields/farfield but does not explicitly state when to use over frequency domain or list prerequisites. Context is clear but lacks exclusions or alternatives.

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

Deploy Server

Other Tools