Skip to main content
Glama
the-real-talk

the-real-talk

add_variable_mode

Add a mode to a Figma variable collection by ID or name and return the new modeId for design system updates.

Instructions

Add a mode to a variable collection (ID or name). Returns the new modeId.

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": {
      "collection": "<collection>",
      "name": "<name>"
    },
    "name": "add_variable_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries full behavioral burden. It usefully discloses the return value ('Returns the new modeId') despite no output schema, but says nothing about permissions, whether adding a mode mutates existing modes, name-collision behavior, or error cases 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and scope, with the return value in a compact trailing clause. Nothing is wasted or buried.

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 a mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin; it covers the return value but leaves parameter meaning and side effects unexplained. The broken $ref in the schema makes an explanatory description more necessary, not less.

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

Parameters2/5

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

Schema description coverage is 0%, and the schema is even ambiguous (the 'name' property is a $ref to 'collection'). The description does add real value by stating the collection may be an ID or a name, but it never clarifies what the required 'name' parameter means (presumably the new mode's name).

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 gives a specific verb and resource ('Add a mode to a variable collection'), which cleanly distinguishes it from the remove/rename/set mode siblings. It stops just short of 5 because it does not explicitly name or contrast with those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites (e.g., that the collection must exist), and no note about when to prefer this over related mode tools like set_explicit_variable_mode. Usage is only inferable from the verb.

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