Define a Setup variable (SVar) for IC-CAP projects, such as sweep ranges like X_LOW or X_HIGH for optimizers. Specify the full variable path and an optional initial value.
Create a Setup variable (SVar). Common uses: X_LOW, X_HIGH, sweep range parameters for optimizers.
| Name | Required | Description | Default |
|---|---|---|---|
| value | No | Initial value | |
| var_path | Yes | Full path, e.g. '/model/dut/setup/VAR_NAME' |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Create' and gives usage examples; it does not mention side effects, overwrite/existence behavior, parent setup requirements, or return values, which are important for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The core purpose is front-loaded, and the usage context is delivered efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 2-parameter creation tool with no annotations or output schema, this is minimally adequate. However, behavioral details such as whether the variable must not already exist, whether the parent setup path is required to already exist, and what happens on failure are left to inference.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: var_path is documented with a full path example and value is documented as 'Initial value'. The description adds semantic context through common use cases, but it does not add parameter-level detail beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Create a Setup variable') and gives concrete common uses (X_LOW, X_HIGH, sweep range parameters for optimizers). This makes it clearly distinguishable from sibling tools like svar_get, svar_set, or other variable-creation tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when the tool is appropriate, namely creating setup-level variables for sweeps and optimizer ranges. It does not explicitly list when-not-to-use alternatives, but the context is clear enough for an agent to infer the main use case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.