Skip to main content
Glama
the-real-talk

the-real-talk

get_local_variables

Lists local Figma variable collections, their modes, and variables with types, per-mode values, and scopes; use the returned cursor to continue partial reads.

Instructions

Read-only: list local variable collections with their modes, and every variable with its type, values per mode and scopes. Read in one pass with a time budget: if it is reached the answer says PARTIAL and gives nextCursor (pass it back as cursor).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_local_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonextCursor of a previous PARTIAL answer, to continue where it stopped
timeBudgetMsNoTime budget of the plugin for this call in ms (default 60000, max 100000). When it is reached the answer says it is PARTIAL and gives nextCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it declares read-only, discloses the time-budget cutoff, states that the reply is marked PARTIAL, and explains that nextCursor must be passed back as cursor. What it does not cover is error behavior or ordering guarantees.

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, front-loaded with the resource being read and the read-only marker, then the pagination contract. Dense but no filler; the second sentence is slightly compressed with three clauses in one breath.

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?

There is no output schema, so the description has to tell the agent what comes back, and it does: collections, modes, variables, type, values per mode, scopes, plus the PARTIAL/nextCursor continuation signal. That is sufficient for an agent to call and resume correctly, though failure modes are unstated.

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 both parameters are already documented in the schema. The description restates the cursor/nextCursor round-trip and references the time budget but adds no format or default details beyond what the schema text already says. Baseline 3 applies.

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 states a specific verb and resource: list local variable collections with their modes, plus every variable with type, per-mode values and scopes. That is concrete enough to distinguish it from the retrieval siblings such as get_local_components or get_styles. It never explicitly contrasts itself with an alternative, though, 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 Guidelines3/5

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

Usage is only implied: it is a read that can be continued with cursor when the answer is PARTIAL. There is no explicit when-to-use versus when-to-use-something-else guidance, no exclusions and no prerequisites. For a read-only enumeration tool that is workable but thin.

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