Skip to main content
Glama
the-real-talk

the-real-talk

boolean_operation

Combine two or more Figma shapes with UNION, SUBTRACT, INTERSECT, or EXCLUDE operations to build complex vector geometry and optionally place the result under a parent node.

Instructions

Combine shapes: UNION, SUBTRACT, INTERSECT or EXCLUDE (2 nodes or more).

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>",
      "operation": "<operation>"
    },
    "name": "boolean_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
nodeIdsYes
parentIdNo
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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, yet it says nothing about whether the source nodes are consumed or preserved, whether a new node is created, whether the result inherits properties from the first node, or what permissions/state are required. For a mutating geometry operation this is a significant gap.

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 short sentence, front-loaded with the verb and resource, with the operation names and cardinality packed in compactly. Nothing is wasted, though the terse phrasing sacrifices clarity on the input node semantics.

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?

With no annotations, no output schema, and 0% parameter description coverage across four parameters, the description should explain at least the outcome of the operation and the two undocumented parameters. As written, an agent cannot predict the result of a SUBTRACT versus EXCLUDE or where the output lands.

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 0%, and the description compensates for part of that by listing the operation enum values and stating the minimum node count. However, the 'name' and 'parentId' parameters remain entirely undocumented in both the schema and the description, leaving half the inputs without meaning.

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?

Description names a specific verb ('Combine') and resource ('shapes') and enumerates the four supported operations, so an agent knows exactly what the tool produces. It stops short of differentiating from other node-producing/combining siblings, which keeps it at 4 rather than 5.

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?

The only usage condition given is a data constraint ('2 nodes or more'), which is already implied by the schema's minItems. There is no guidance on when to prefer this tool over other combination approaches or what preconditions the input nodes must satisfy.

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