Skip to main content
Glama
Sign In
CST-MCP

CST-MCP

by woson-L
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cst_generate_mesh_tool

Generates a simulation mesh in CST Studio Suite through its Python automation API, covering a capability not exposed by CST's VBA API.

Instructions

Mesh generation is not exposed through CST's VBA API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cst_generate_mesh_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a limitation but says nothing about what happens when the tool is called, whether it returns a message, errors out, or has side effects. This is inadequate transparency for any invocable tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is a single short sentence, so it is not verbose. However, it is under-specified rather than appropriately concise: it does not front-load a usable purpose or actionable guidance, and the one sentence does not earn its place as a tool description.

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?

An output schema exists, so return values need not be explained. Still, the description omits critical context such as whether this tool is a stub, what it actually does, and what an agent should use instead for mesh operations. For a generate tool with a contradictory-sounding limitation, this is incomplete.

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 tool has zero parameters and schema description coverage is 100%, so there are no parameter semantics to document. The description does not need to add parameter information, making the baseline 4 appropriate.

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

Purpose1/5

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

The description does not state what the tool does. It only asserts that mesh generation is not exposed through CST's VBA API, which is a negative limitation rather than a specific verb and resource. For a tool named cst_generate_mesh_tool, this leaves the actual purpose unclear and potentially misleading.

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

Usage Guidelines1/5

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

There is no guidance on when or when not to use this tool. It does not name an alternative such as cst_set_mesh_tool, nor does it explain whether the tool should ever be invoked. An agent is left with no routing information.

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