Skip to main content
Glama
the-real-talk

the-real-talk

set_corner_radii

Set individual px corner radii on a Figma node; specify any combination of top-left, top-right, bottom-left, and bottom-right, leaving omitted corners unchanged.

Instructions

Set each corner radius separately (values in px; omitted corners are left as they are). To link a corner to a variable use bind_variable CORNER_TOP_LEFT etc.

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_corner_radii"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the node
topLeftNo
topRightNo
bottomLeftNo
bottomRightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose two useful behavioral facts — units are px and omitted corners are left unchanged, meaning partial updates are non-destructive — but says nothing about prerequisites (must the node be a frame/rectangle?), failure behavior, or what the response looks like for a mutation.

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?

Two short sentences, parenthetical unit/omission rule folded in efficiently, and the alternative tool is mentioned last where it belongs. Nothing is wasted.

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

Completeness4/5

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

For a low-complexity five-parameter mutation with no output schema and no annotations, the description covers the essential semantics — units, partial-update behavior, and the variable-binding escape hatch. Only the node-type prerequisite and error behavior are absent, which is minor at this complexity.

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 coverage is only 20%, with just nodeId documented, so four corner parameters rely entirely on their names. The description adds the px unit and the omission-equals-unchanged rule, which is genuinely useful, but does not explicitly tie the values to topLeft/topRight/bottomLeft/bottomRight or note whether corners are independent per-side.

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?

States a specific verb and resource ('Set each corner radius separately'), and the phrase 'separately' implicitly distinguishes it from the sibling set_corner_radius, which presumably sets a uniform radius. It stops short of naming that sibling explicitly, so an agent still has to infer the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete routing for an adjacent need: linking a corner to a variable should go through bind_variable with CORNER_TOP_LEFT and similar tokens. It offers no exclusion rule against set_corner_radius or other radius-adjacent siblings, so the contrast is only implied.

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