Skip to main content
Glama
runkids

figlens

by runkids
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

variables

Extracts design tokens bound by a frame—collections, modes, and aliases—from a saved .fig file, or all local tokens when no node is given.

Instructions

The variables a frame binds (collections, modes, aliases); without a node, every local variable.

Input Schema

NameRequiredDescriptionDefault
fileYesthe saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root
nodeNothe node, including full instance sublayer IDs; omit for every local variable

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +true
    • changedInput schema / properties / file / description
      Previous value: -"the .fig file (File > Save local copy): an absolute path, or gs://bucket/object"New value: +"the saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root"
    • addedInput schema / properties / file / minLength
      Added value: +1
    • changedInput schema / properties / node / description
      Previous value: -"the frame; omit for every local variable"New value: +"the node, including full instance sublayer IDs; omit for every local variable"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the scope behavior when node is omitted, but it does not explicitly confirm that the operation is read-only, nor does it describe permissions, error conditions, or return shape beyond naming the variable categories.

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?

The definition is a single compact sentence that front-loads the resource and appends the key scoping rule. It is efficient and avoids repetition, though the sentence fragment form is slightly less immediately scannable than a full verb-led statement.

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?

With two well-documented parameters and no output schema, the description covers the core scoping behavior needed to call the tool. However, for a query tool with no annotations, it could do more to confirm read-only safety and describe what the returned variable data contains.

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 input schema. The description reinforces the node-omission behavior with 'every local variable,' but adds no syntax or format details beyond what the schema provides, making the baseline score of 3 appropriate.

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 identifies the resource precisely: variables bound by a frame, including collections, modes, and aliases, and clarifies the default scope when no node is given. It is not phrased as a verb, but an agent can still tell this tool apart from siblings like tree, find, or inspect because it names a distinct data type.

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?

The phrase 'without a node, every local variable' gives a clear condition for the optional node parameter, but the description does not explain when to use this tool instead of siblings such as inspect or nodes. Usage is implied by the resource name rather than explicitly guided.

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