Skip to main content
Glama
guardianer9-debug

CST Studio Orchestrator MCP

cst_create_anisotropic_material

Define anisotropic materials with distinct permittivity, permeability, and loss tangent along each axis for modeling crystals, metamaterials, and composite substrates.

Instructions

Create an anisotropic material with per-axis permittivity, permeability, and loss tangent values. Used for crystals, metamaterials, and composite substrates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mu_xYesRelative permeability along X
mu_yYesRelative permeability along Y
mu_zYesRelative permeability along Z
nameYesMaterial name
tan_d_xNoElectric loss tangent along X
tan_d_yNoElectric loss tangent along Y
tan_d_zNoElectric loss tangent along Z
epsilon_xYesRelative permittivity along X
epsilon_yYesRelative permittivity along Y
epsilon_zYesRelative permittivity along Z
Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It only says 'create' but does not specify if the material is stored in a project, requires an open project, or has any side effects. The burden is not fully met.

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 that are concise and front-loaded: first sentence states the action and parameters, second sentence provides use cases. No extraneous information.

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 and no annotations, the description is fairly complete for a creation tool. It covers what the tool does and the key parameters. However, it lacks context about project dependencies (e.g., whether a project must be open) or return values.

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 description coverage is 100%, so the baseline is 3. The description adds a summary of parameter types (permittivity, permeability, loss tangent) but does not provide additional constraints, relationships, or examples beyond what the schema already contains.

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 an anisotropic material with per-axis properties, and mentions specific use cases (crystals, metamaterials, composite substrates). This distinguishes it from other material creation tools like isotropic materials (cst_create_material) or special materials.

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 lists typical applications but does not explicitly state when to use this tool versus alternatives (e.g., isotropic materials, ferrites). No 'when not to use' or exclusion criteria are provided, leaving the agent to infer from the name and parameters.

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