Set a global variable in an Easy Spec project to store reusable values. Specify the variable name and value, optionally with a project path, to make it available across flows and scenarios.
Set a global variable (Variables tab).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| value | Yes | ||
| project | No | Path to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted. |
Changes observed during successful MCP inspections.
v1.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist and the description does not disclose side effects, such as overwriting existing variables or requiring specific permissions. The behavior is not transparent beyond the basic action of setting a variable.
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?
The description is extremely concise, consisting of a single short sentence with no redundant information. It is well-structured and easy to parse quickly.
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?
The description is adequate for a simple setter but lacks context about the variable lifecycle, potential overwrites, or return values. Given the large number of sibling tools, more contextual guidance would be helpful.
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?
Only the 'project' parameter has a description, leaving 'name' and 'value' without explicit semantics. Schema coverage is 33%, which is low, and the description does not compensate by explaining these parameters.
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 clearly states the tool sets a global variable and references the Variables tab, which distinguishes it from state variables. However, it does not explicitly name sibling alternatives like set_state_var.
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?
No guidance is provided on when to use this tool versus alternatives such as set_state_var, unset_variable, or get_variables. The description lacks any conditional or contextual usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.