Skip to main content
Glama
the-real-talk

the-real-talk

set_stroke_options

Set a node's stroke alignment (INSIDE, OUTSIDE, CENTER) and/or stroke weight to control border appearance in Figma designs.

Instructions

Set the stroke alignment (INSIDE, OUTSIDE, CENTER) and/or the stroke weight of a node.

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": "set_stroke_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
alignNo
nodeIdYesID of the node
weightNo

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?

With no annotations, the description carries the full behavioral burden. It reveals that alignment and weight can be set independently, but does not disclose mutation side effects, permission requirements, default behavior when only one field is supplied, or weight units.

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 definition is a single, front-loaded sentence with no wasted wording. It communicates the two settable properties efficiently.

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 mutation tool with no annotations, no output schema, and incomplete parameter coverage, the description is too sparse. It should specify weight units, default/preservation behavior, and any permission or side-effect considerations.

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 only 33%, so the description should compensate more. It clarifies that alignment and weight are independently optional and lists the allowed alignment values, but it does not explain weight units or the effect of omitting either optional parameter.

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 states a specific verb and resource: it sets stroke alignment and/or stroke weight on a node, and it names the alignment values. This distinguishes it from siblings like set_stroke_color, though it does not explicitly call out that distinction.

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, nor any stated prerequisites or exclusions. The 'and/or' phrasing implies both settings are optional, but the agent must infer usage context entirely.

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