Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

annotate_hierarchy

Annotate a Figma frame with heading levels, reading order, and focal points to clarify its visual hierarchy for designers and reviewers.

Instructions

Annotate the visual hierarchy: heading levels, reading order, focal points.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "annotate_hierarchy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesFrame to annotate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

A3.5/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 full responsibility for behavioral disclosure. It says 'Annotate' but does not explain whether this creates persistent annotations, modifies document state, replaces existing annotations, or returns anything. For a mutation-like tool this is a meaningful gap.

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?

A single, front-loaded sentence with no filler. Every word contributes meaning, and the key specifics are listed compactly.

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?

The tool has a simple one-parameter schema and a clear purpose, but there is no output schema and no annotation metadata. The description does not explain what the annotation result looks like or whether it modifies the document, so it is not fully complete for an agent.

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 the schema already documents that nodeId is the frame to annotate. The description does not add further parameter semantics, but per the baseline with high schema coverage this is acceptable.

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 ('Annotate') and resource ('visual hierarchy'), then specifies the exact aspects covered: heading levels, reading order, focal points. This clearly distinguishes it from sibling annotate_* tools like annotate_spacing, annotate_colors, annotate_typography.

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 described scope implies when this tool should be used, but there is no explicit guidance about when not to use it or which sibling tool to choose instead. Listing the specific hierarchy aspects gives some context, but leaves routing to the agent's inference.

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