Skip to main content
Glama
runkids

figlens

by runkids
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

tree

Lists node IDs, types, and names under a chosen root in a saved .fig file, helping locate pages and frames when their names are unknown.

Instructions

List node ids, types and names under a chosen root. A shallow outline locates pages and frames when their names are unknown; find searches known names or visible text directly.

Input Schema

NameRequiredDescriptionDefault
fileYesthe saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root
jsonNonested {id,type,name,children} JSON instead of indented text (about 1.6x larger)
nodeNoa stored root id; default the whole document; use inspect for instance sublayers0:0
depthNolevels to list below the root

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +true
    • addedInput schema / properties / depth / maximum
      Added value: +18446744073709552000
    • addedInput schema / properties / depth / minimum
      Added value: +0
    • 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
    • addedInput schema / properties / json / default
      Added value: +false
    • addedInput schema / properties / node / default
      Added value: +"0:0"
    • changedInput schema / properties / node / description
      Previous value: -"the root; default the whole document"New value: +"a stored root id; default the whole document; use inspect for instance sublayers"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It implies a read-only listing operation and describes the returned fields (ids, types, names), but it does not explicitly state side-effect safety, permissions, or rate limits. The schema covers the output-mode parameter details, so this is adequate rather than rich.

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 two sentences with no wasted wording. The core purpose is front-loaded, and the comparison to 'find' is placed immediately after as useful routing context.

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?

For a read-only outline tool with a fully described schema, the description is nearly complete: it states what is returned and when to use it versus find. The main missing piece is explicit differentiation from the sibling 'nodes,' but no critical calling information is absent.

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 parameter meanings are already fully documented in the input schema. The description adds only the high-level notion of listing 'under a chosen root' and a 'shallow outline,' which aligns with the root and depth parameters but does not add syntax or usage detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 node ids, types and names under a chosen root.' It also distinguishes the tool from the sibling 'find' by explaining that tree is for locating pages/frames when names are unknown, while find searches known names or visible text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a clear use case ('when their names are unknown') and explicitly names the alternative tool ('find searches known names or visible text directly'). It does not cover when to prefer or avoid the other siblings such as inspect or nodes, but the main routing decision is clear.

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