Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_variable_collection

Create a design token collection with named modes such as Light and Dark to organize variables for multi-theme design systems.

Instructions

Create a design token collection with modes (e.g. Light/Dark).

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

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name (e.g. "Colors", "Spacing")
modesNoMode names, e.g. ["Light", "Dark"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

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 burden of behavioral disclosure. It only restates the basic creation operation and the notion of modes, without mentioning side effects, duplicate handling, document scope, prerequisites, or whether existing token collections are affected.

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?

The description is a single focused sentence with no filler. The core action, resource, and a clarifying example are all front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter create operation, the description covers the essential action and resource. However, with no annotations and no output schema, it leaves usage context, return behavior, and edge cases unspecified, making it adequate but not complete.

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 the baseline is 3. The description's mode example ('Light/Dark') largely echoes the schema's example and does not add substantive semantics beyond what the schema already documents.

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 concrete action ('Create') on a specific resource ('design token collection') and clarifies it supports modes with an example like 'Light/Dark'. It distinguishes the resource from siblings like create_variable because it names a collection, but it does not explicitly differentiate itself from create_design_tokens.

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?

Provides no guidance on when to use this tool versus alternatives such as create_variable, create_design_tokens, import_tokens, or swap_mode. The 'modes' example implies a use case, but there is no explicit when-to-use or exclusionary context.

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