Skip to main content
Glama
the-real-talk

the-real-talk

set_variable_scopes

Restrict where a design variable applies by replacing its allowed scopes, such as fills, text, spacing, radius, or opacity, to keep tokens used correctly.

Instructions

Limit where a variable can be used (scopes such as ALL_SCOPES, GAP, CORNER_RADIUS, WIDTH_HEIGHT, ALL_FILLS, FRAME_FILL, SHAPE_FILL, TEXT_FILL, STROKE_COLOR, TEXT_CONTENT, OPACITY, FONT_SIZE...). Replaces the existing scopes.

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>",
      "scopes": "<scopes>"
    },
    "name": "set_variable_scopes"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopesYesAllowed usages
variableIdYesID of the variable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the most important behavioral fact — 'Replaces the existing scopes' — which tells the agent this is an overwrite, not an additive change. However it omits whether prior scopes are recoverable, whether ALL_SCOPES must be the only entry, and any permission or error conditions.

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?

Two sentences, with the core action and the replacement behavior both front-loaded. The enumerated scope list duplicates the schema enum and is the one piece of trimming that would improve it.

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?

The two required parameters are fully documented by the schema and there is no output schema to explain, so the essentials are covered. Still missing are the consequences for downstream bindings or usages of the variable after scopes are replaced, which matters for an overwrite operation.

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% and the enum values are fully enumerated in the schema, so the description's parenthetical list of scope names is largely redundant. It adds no meaning about how the variableId parameter is obtained or how scope values interact.

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 opens with a specific verb-plus-resource statement ('Limit where a variable can be used') that is clearly distinct from siblings like set_variable_alias or set_variable_description. It does not explicitly name siblings, but the operation itself is unambiguous.

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 by the purpose statement; there is no explicit when-to-use or when-not-to-use guidance, and no note on how it relates to sibling setters that configure variable metadata. Adequate but leaves the agent to infer intent.

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