Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

measure_distance

Measure the distance between two Figma nodes by providing their IDs. Get precise spacing to validate design layouts.

Instructions

Measure distance between two nodes.

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": {
      "nodeId1": "<nodeId1>",
      "nodeId2": "<nodeId2>"
    },
    "name": "measure_distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeId1YesFirst node
nodeId2YesSecond node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without revealing units, coordinate system, whether distances are based on bounding boxes or center points, or what the return value looks like. It does not contradict any annotations because none exist, but it provides minimal behavioral insight.

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 description is a single concise sentence with no wasted words, and the core action is front-loaded. It is slightly under-specified, but that issue is already captured by other dimensions; the structure itself is clean and efficient.

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 simple two-parameter tool with no output schema and no annotations, the description is not fully complete. An agent would not know the unit of measurement, the reference points used, or the exact shape of the result. Since the output schema is absent, the description should have explained the return value, but it does not.

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%, with both parameters documented as 'First node' and 'Second node.' The description adds no extra meaning beyond the schema, but the schema already adequately explains the two parameters, so the baseline of 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 clearly states a specific verb and resource: 'Measure distance between two nodes.' It is not a tautology and conveys the core function. However, it does not explicitly differentiate itself from related sibling tools like create_measurement or annotate_spacing, which could also involve distance-related functionality.

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 guidance on when to use this tool versus alternatives. No mention of use cases, prerequisites, or exclusions. For example, it does not clarify the difference between returning a numeric distance and creating a persistent measurement annotation, which is likely relevant given sibling tools like create_measurement.

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