Skip to main content
Glama
the-real-talk

the-real-talk

swap_instance

Swaps a selected instance for another local component, enabling nested instance swaps in Figma designs.

Instructions

Swap an instance to another local component (for a nested INSTANCE_SWAP).

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>",
      "componentId": "<componentId>"
    },
    "name": "swap_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
componentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 mentions the local-component constraint but says nothing about effects on overrides, reversibility, permissions, or what happens to the previous component instance.

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 definition is a single efficient sentence with the core action front-loaded. It is not bloated, though its brevity leaves important operational details unstated.

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?

This is a mutation tool with no annotations, no output schema, and no parameter descriptions. One sentence is insufficient to make the tool safely and correctly invocable without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate but does not. It only loosely implies that nodeId identifies the instance and componentId identifies the replacement, and it adds a "local component" constraint, but neither parameter's format or role is explained.

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 names a specific verb and resource: "Swap an instance to another local component." The parenthetical clarifies that this targets a nested INSTANCE_SWAP, which helps distinguish the operation, though it does not contrast with siblings like detach_instance or set_instance_properties.

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 context is "for a nested INSTANCE_SWAP." There is no explicit guidance on when to choose this tool over detach_instance, create_component_instance, or set_instance_properties, nor any prerequisite or exclusion conditions.

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