Skip to main content
Glama
guardianer9-debug

CST Studio Orchestrator MCP

cst_create_lorentz_material

Create a Lorentz oscillator material to model resonant dielectric behavior near absorption bands for glass, crystals, and optical materials.

Instructions

Create a Lorentz oscillator dispersive material. Models resonant dielectric behaviour near absorption bands: eps(w) = eps_inf + delta_eps * w0^2 / (w0^2 - w^2 + jgammaw). Used for glass, crystals, and optical materials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMaterial name (e.g. 'Optical Glass')
epsilon_infYesHigh-frequency permittivity limit
delta_epsilonYesOscillator strength (permittivity increment)
damping_freq_ghzYesDamping (collision) frequency in GHz
resonant_freq_ghzYesResonant frequency in GHz
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes the mathematical model but does not disclose behavioral aspects such as whether it modifies existing materials, requires permissions, or has 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.

Conciseness4/5

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

The description is concise with two sentences, includes the formula, and is front-loaded with the primary purpose. Minor improvement could be simplifying the formula presentation.

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 sibling material creation tools, the description does not provide enough guidance on when to use Lorentz vs. other models. It mentions use cases but lacks comparative context for an AI agent to decide.

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 already covers all parameters with descriptions (100% coverage), but the description adds value by providing the equation that contextualizes the parameters (e.g., resonant frequency, damping).

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's function: 'Create a Lorentz oscillator dispersive material' and provides the mathematical formula, distinguishing it from sibling material creation tools like Debye or Drude models.

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 ('glass, crystals, and optical materials') but does not explicitly compare to alternatives or state when not to use it, leaving the agent to infer appropriate contexts.

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