Skip to main content
Glama
Sign In
CST-MCP

CST-MCP

by woson-L
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cst_assign_material_tool

Assign an existing material to a solid in CST Studio Suite through the CST-MCP server, setting its material for 3D modeling and simulation setup.

Instructions

Assign an existing material to a solid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "solid": "<solid>",
      "material": "<material>"
    },
    "name": "cst_assign_material_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
solidYes
materialYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden for a mutation tool. It says what action occurs but does not disclose side effects, whether an existing material assignment is overwritten, required permissions, or any failure behavior.

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 a single front-loaded sentence with no wasted words, which is structurally efficient. It is arguably too terse for the operation's missing context, but the conciseness itself is strong.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a mutation tool with no annotations, 0% schema description coverage, and only basic required parameters, the description is substantially incomplete. The output schema covers return values, but missing prerequisites and side-effect details leave the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter has a description. The prose names 'solid' and 'material' only in passing, adding no format, naming convention, or identification details beyond the schema's property names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Assign') and resource ('existing material to a solid'), making the operation understandable without opening the schema. It also implicitly distinguishes itself from material creation or library loading by saying 'existing material,' though it does not explicitly name sibling tools.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative-tool guidance is provided. The description implies the basic operation but does not explain prerequisites such as whether the solid and material must already exist in the project.

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