Skip to main content
Glama

create_configuration

Create a configuration on the active part or assembly to vary component/feature suppressions and dimension values while sharing base geometry, enabling variants without file duplication.

Instructions

Crear una configuración nueva en la pieza o ensamble activo.

Una configuración es metadata: comparte la geometría base pero permite variar supresiones de componentes/features y valores de dimensiones. Es la vía v1 para variantes (trim, tamaño, opcionales) sin duplicar archivos. [en: Create a new configuration on the active part or assembly. A configuration is metadata: shares base geometry but lets you vary component/feature suppressions and dimension values — the v1 path for variants without duplicating files.]

Args: name: New configuration name (must be unique; idempotent if it exists). parent: Optional parent configuration name (for derived configs). description: Optional description for the configuration.

Returns the configuration name.

Gotcha (verificado en vivo): crear la configuración la ACTIVA — la config activa ya no es la anterior. Lee active_config antes de confiar en operaciones "scoped" subsecuentes, y reactiva la config original si no querías cambiarte.

Related: build_variant_family (one call to create N configurations that vary suppressions and dimensions — use this when the user asks for "small/medium/large" or "M6/M8/M10" trim variants instead of N separate create_configuration calls).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
parentNo
descriptionNo
Behavior5/5

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

No annotations provided, but description adds crucial behavioral context: creating a configuration activates it (changes active config), and it is idempotent. The 'Gotcha' section highlights a live-verified side effect.

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?

Well-structured with sections (description, args, gotcha, related tool), front-loaded with purpose. Slightly long but not verbose.

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

Completeness5/5

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

Given no output schema and no annotations, the description covers the tool's purpose, side effects, parameter semantics, and alternatives. Fully adequate for agent to select and invoke correctly.

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 0%, so description compensates by explaining each parameter: name is unique and idempotent, parent is for derived configs, description is optional. Adds meaningful context 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 'Crear una configuración nueva en la pieza o ensamble activo' with specific verb and resource. It distinguishes from sibling tool build_variant_family by explaining when to use that alternative.

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

Usage Guidelines5/5

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

Explicitly provides when to use build_variant_family instead of create_configuration, and mentions idempotency for name. Gives clear context for usage.

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/danielproxd2/MCP_CAD'

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