Skip to main content
Glama

Generate a stochastic variant pack from a seed look

variant_pack

Generates perturbed parameter variants around a seed look, clamps to slider ranges, and writes a morph_pack-compatible JSON file to the Obsidian vault.

Instructions

Generate N perturbed variants around an anchor parameter look and write the whole pack to the Obsidian vault as a morph_pack-compatible JSON. Probes the target COMP's customPars for slider ranges to clamp + integer-round per param, then perturbs each variant uniformly within ±delta_range × (normMax − normMin). The resulting file is consumed directly by morph_pack (action=unpack). Requires TDMCP_VAULT_PATH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPack name. File defaults to MorphPacks/<name>.morphpack.json.
parentNoParent COMP recorded into provenance.container_path./project1
comp_pathNoCOMP whose customPars give slider ranges for clamping. Defaults to target_path else parent.
seed_lookYesAnchor look: { paramName: number }. Names must be numeric custom pars on comp_path.
countNoNumber of perturbed variants (1..64).
delta_rangeNoPerturbation magnitude as fraction of each param's slider span.
seedNoRNG seed for repeatable packs.
variant_prefixNoSlot id prefix.
include_seedNoIf true, slot v00 is the seed look itself.
target_pathNoRecorded into provenance.target_path so morph_pack can unpack standalone.
interpolationNoRecorded into provenance.linear
vault_pathNoOverride default MorphPacks/<name>.morphpack.json. Resolved via Vault.resolve.
overwriteNoAllow replacing an existing pack file.
Behavior5/5

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

The description explains the perturbation process, clamping, and vault writing. Annotations already indicate non-destructive and mutating behavior, which aligns with the description. No contradictions.

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 description is concise (3 sentences) and front-loaded with the main action. Every sentence adds meaningful information without verbosity.

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?

Given 13 parameters and no output schema, the description covers the essential behavior (probing, clamping, vault writing) and prerequisites. It does not detail return values, but that is acceptable without output schema.

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 baseline is 3. The description adds value by explaining the overall process (clamping, uniform perturbation) and linkage to morph_pack, enhancing understanding beyond schema.

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 clearly states the tool generates perturbed variants and writes them to the vault as a JSON file. It distinguishes from sibling tools like morph_pack, which consumes the output.

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?

The description references prerequisites (TDMCP_VAULT_PATH) and mentions morph_pack as the consumer, providing context on when to use this tool. However, it does not explicitly state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server