Skip to main content
Glama
guardianer9-debug

CST Studio Orchestrator MCP

cst_matching_pi_network

Design a Pi-section impedance matching network with controllable Q factor for RF impedance matching between source and load.

Instructions

Design a Pi-section impedance matching network (C-L-C or L-C-L). Uses two back-to-back L-sections via a virtual resistance for controllable Q factor. Pure Python computation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
q_factorNoDesired loaded Q factor. Must be > sqrt(R_large/R_small - 1). If omitted, a default Q is chosen automatically.
z_load_imagNoLoad reactance in ohms (default 0)
z_load_realYesLoad resistance in ohms
frequency_ghzYesDesign frequency in GHz
z_source_imagNoSource reactance in ohms (default 0)
z_source_realYesSource resistance in ohms
Behavior3/5

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

States 'Pure Python computation' but no annotations exist. Does not disclose side effects, output format, or if it modifies any data. Adequate but lacks depth for a computation-heavy tool.

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 sentences with no redundancy. Front-loaded with key purpose and method. Efficiently conveys essence.

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?

Lacks explanation of output (e.g., does it return component values?). Given no output schema, description should cover this. Basic topology info is present but incomplete for practical use.

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 parameters are already described. The description adds no extra meaning beyond the schema; mentions Q factor but that is also in schema. Baseline 3.

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?

Description clearly states it designs a Pi-section impedance matching network with specific topologies (C-L-C or L-C-L) and mentions the method (back-to-back L-sections). This is distinct from sibling tools like L-network or T-network.

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?

Implies use for controllable Q factor but does not explicitly state when to choose Pi over other matching networks (e.g., L-network or T-network). No exclusions or alternative guidance provided.

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