Skip to main content
Glama
the-real-talk

the-real-talk

set_variable_alias

Create a variable alias for a specific mode, linking one variable to another of the same type. Use it to keep mode-specific values synchronized in Figma design systems.

Instructions

Make a variable, for one mode, an alias of another variable (same type).

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": {
      "variableId": "<variableId>",
      "mode": "<mode>",
      "aliasVariableId": "<aliasVariableId>"
    },
    "name": "set_variable_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
variableIdYes
aliasVariableIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It signals a mutation and mentions the same-type constraint, but says nothing about overwriting an existing alias, what happens on type mismatch, required permissions, or reversibility.

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?

A single front-loaded sentence with no filler, and the parenthetical '(same type)' efficiently carries a real constraint. It is perhaps too terse, but nothing is wasted.

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?

For an unannotated mutation tool with zero schema description coverage and no output schema, the description is thin. An agent would not know the mode argument's form, whether the alias target must already exist or be in the same collection, or what errors to expect on mismatched types.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It does loosely map the three arguments (the variable, the single mode, the other variable), but gives no indication whether 'mode' is a name or an ID, nor any format or lookup guidance.

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 names a specific verb+resource operation: making one variable an alias of another. It adds two meaningful qualifiers, that the alias applies 'for one mode' and requires the same type, which distinguish this from general binding or value-setting siblings.

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?

Usage is only implied: the agent can infer this is the tool for creating alias relationships rather than direct values. There is no explicit when-to-use vs. alternatives such as bind_variable or set_variable_value, and no stated prerequisites for the two variables involved.

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