Skip to main content
Glama
guardianer9-debug

CST Studio Orchestrator MCP

cst_get_s_parameters

Extract S-parameter results (magnitude, phase, real/imaginary) from a completed CST simulation for specified input and output ports.

Instructions

Extract S-parameter results from a completed CST simulation. Returns S-parameter data (magnitude, phase, real/imaginary) for the specified port pair. In connected mode reads directly from the result tree; in offline mode returns VBA scripts and explains the CST result tree structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format for S-parameter data. 'db' = magnitude in dB, 'mag' = linear magnitude, 'real_imag' = real and imaginary parts, 'phase' = phase in degrees.db
port_inNoInput port number (excitation port).
port_outNoOutput port number (observation port).
Behavior3/5

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

No annotations provided; the description discloses dual-mode behavior and return content, but lacks information on prerequisites (e.g., simulation must be completed), error conditions, or side effects. It does not confirm read-only nature.

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 two efficient sentences: first defines the core purpose, second explains the two modes. Every sentence is meaningful with no redundancy.

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 no output schema, the description covers the tool's purpose, output data types, and operational modes. However, it lacks details on the structure of the returned data and error handling, which would be helpful for an agent.

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%, and the description only paraphrases the format and port parameters already defined in the schema. It adds no new semantics or constraints beyond what the schema 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?

The description clearly states the tool extracts S-parameter results from completed CST simulations, specifies the return data types (magnitude, phase, real/imaginary), and distinguishes it from the more specific sibling 'cst_get_s_parameter_phase' by being general-purpose.

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 implies usage after a completed simulation and explains two operational modes (connected vs offline), but does not explicitly state when to use this tool over alternatives like 'cst_get_s_parameter_phase' or other extraction tools.

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