Skip to main content
Glama
the-real-talk

the-real-talk

set_variable_value

Update an existing design variable's value for a specific mode, including color values in hex or RGBA format.

Instructions

Set the value of an existing variable for one mode. Colors are #RRGGBB(AA) or {r,g,b,a} in 0-1.

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>",
      "value": "<value>"
    },
    "name": "set_variable_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesMode name or mode ID
valueYesNew value, matching the variable type
variableIdYesID of the variable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two useful constraints — the variable must already exist, and the write is scoped to a single mode — but says nothing about permissions, error behavior when the value type mismatches, or whether the change is reversible.

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?

Two sentences, front-loaded with the primary action and followed by the one format detail an agent could plausibly get wrong. Nothing is wasted and nothing is buried.

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?

For a three-parameter mutation tool with no output schema and complete schema coverage, the description covers the essential scope and value-format questions. The remaining gap is behavioral (failure modes, cross-mode effects) rather than something needed to construct a valid call.

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 100%, so all three parameters are documented structurally, and the description adds a color-format hint. However, the hex pattern and the 0-1 r/g/b/a bounds are already encoded in the schema, so the guidance largely restates structured data rather than extending it.

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?

States a specific verb and resource: 'Set the value of an existing variable for one mode.' This clearly separates it from sibling setters like set_variable_alias or set_variable_description, which change metadata rather than the value itself, though those alternatives are never named.

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: 'existing variable' tells the agent this mutates rather than creates, and 'for one mode' scopes the effect. There is no explicit guidance on when to choose this over create_variable or the other set_variable_* tools, and no mention of what happens to values in other modes.

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