Skip to main content
Glama
the-real-talk

the-real-talk

combine_as_variants

Merge COMPONENT nodes into a component set (variants) by naming each with variant properties like Style=Geste; place the new set in a specified parent or the first component's parent.

Instructions

Combine COMPONENT nodes into a component set (variants). Name each component beforehand like "Style=Geste, Taille=Normale" to define the variant properties. The set is created in parentId, or in the parent of the first component.

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": {
      "nodeIds": "<nodeIds>"
    },
    "name": "combine_as_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the set
nodeIdsYesIDs of the components
parentIdNoParent of the new set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the core operation and the naming prerequisite but omits critical mutation details: whether original components are consumed, required permissions, error handling if names are malformed, and what the tool returns.

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?

Three sentences with zero waste: purpose first, then the naming requirement, then placement logic. The structure is front-loaded and each sentence earns its place.

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?

For a mutation tool with no annotations and no output schema, the description covers the core action and a key naming prerequisite. However, it leaves gaps around side effects, permissions, and error conditions that an agent would need to invoke it safely.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining that parentId determines the set's location with a fallback to the parent of the first component. It also clarifies that component names must follow a specific format to define variant properties, which affects the nodeIds 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 ('Combine') and resource ('COMPONENT nodes into a component set (variants)'), making the operation clear. It does not explicitly contrast with sibling tools like create_component or convert_to_component, so an agent must infer that this operates on existing components rather than creating new ones.

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?

It implies usage by instructing to name components beforehand to define variant properties, which is a key prerequisite. However, it offers no explicit when-to-use guidance versus alternatives such as create_component, and no when-not conditions or exclusions.

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