Skip to main content
Glama
the-real-talk

the-real-talk

flatten_nodes

Combine multiple Figma nodes into one vector to simplify complex layers and prepare designs for export or editing.

Instructions

Flatten nodes into a single vector.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
nodeIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of disclosure. It does not say that flattening merges/replaces the source nodes, whether the action is reversible, what happens to children or overrides, or what the caller gets back. Only the fact that it is a mutation is implied by "flatten".

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?

A single front-loaded sentence with no filler or redundant clauses. It is efficient, though its brevity comes partly from omitting important information rather than from tight editing.

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

Completeness2/5

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

For a destructive geometry-mutating tool with two undocumented parameters, no annotations, and no output schema, the definition is far too thin. Critical facts about node replacement, required minimum selection, and the result are all missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description says nothing about either parameter. It does not explain that nodeIds selects the nodes to merge (with a 1-200 item constraint) or that name labels the resulting vector layer, so an agent must infer both from the schema alone.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence states a verb ("flatten") and a result ("into a single vector"), which is clearer than the bare tool name, but it largely restates the name and adds no scope detail. It does not distinguish this operation from nearby operations like group_nodes, boolean_operation, or combine_as_variants.

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?

There is no when-to-use or when-not-to-use guidance and no mention of an alternative tool. An agent cannot tell from this text whether flattening is the right choice versus grouping or boolean-combining the same nodes.

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