Skip to main content
Glama
Sign In
RFingAdam

mcp-cst-studio

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cst_set_parameter

Set or create a design parameter in CST Studio. Parameters can hold numeric values or string expressions referencing other parameters.

Instructions

Set or create a design parameter in CST Studio. Parameters can hold numeric values or string expressions referencing other parameters.

Input Schema

NameRequiredDescriptionDefault
nameYesParameter name (e.g. 'patch_length', 'substrate_h').
valueYesParameter value. A number (e.g. 10.5) or a string expression referencing other parameters (e.g. 'patch_length / 2').
descriptionNoOptional human-readable description of the parameter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Since no annotations are present, the description is vital in explaining that parameters can be either literal numeric values or complex string expressions that reference other parameters. This ability to handle inter-parameter dependencies is a key behavioral trait provided by the text.

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?

The description is extremely concise, using two focused sentences. Each sentence serves a distinct purpose, front-loading the function and then detailing the critical capabilities of the tool.

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 the simplicity of the API (setting a name and a value), the description provides all necessary information for an agent to formulate a correct tool call. It clearly defines the complexity of the `value` field.

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 description adds significant meaning by specifying the allowed types for the 'value' parameter. It clarifies that values are not limited to constants but can be dynamically calculated strings referencing other design elements.

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 clearly states the primary function as setting or creating a design parameter within CST Studio. This identifies the action and resource immediately, which is helpful for distinguishing it from retrieval tools like cst_get_parameter.

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 usage is implied by the 'set or create' nature of the tool. While it doesn't explicitly state 'use this instead of cst_delete_parameter,' its action is clear as a modification/creation operation.

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