Skip to main content
Glama
the-real-talk

the-real-talk

remove_variable_mode

Removes a variable mode by ID or name from a specified collection, helping you clean up unused modes in Figma design systems.

Instructions

Remove a mode (ID or name) from a collection.

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>",
      "mode": "<mode>"
    },
    "name": "remove_variable_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 the full burden. It says "Remove" but never states whether the removal is destructive or reversible, what happens to variables still bound to that mode, or whether special permissions are needed. For a mutation tool with zero annotation coverage this is a significant gap.

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 tight sentence with the key constraint front-loaded and no filler. It is efficient, though its brevity is part of why other dimensions are thin.

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?

Given a destructive mutation with no annotations, no output schema, and no parameter documentation, the definition is too thin. An agent calling it correctly would need to know side effects on bindings and how the collection argument is identified.

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 itself is unhelpful (the mode property is a $ref to the collection string). The description does add one useful fact, that the mode may be given by ID or name, but the required collection parameter is left entirely unexplained.

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 ("Remove a mode") plus the scope ("from a collection"), which is enough to identify the operation. It does not differentiate itself from the sibling add_variable_mode or explain how it differs from related mode tools such as set_explicit_variable_mode, so it stops short of a 5.

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 guidance on when to use this tool versus alternatives, and no prerequisites or exclusions are stated. The agent must infer usage entirely from the name and the one-line description.

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