Skip to main content
Glama

add_element

Add an ArchiMate element to the active model. Specify type and name, optionally set description, folder, properties, or stable ID.

Instructions

Add a new ArchiMate element to the active model.

Call `list_supported_types` to discover valid `element_type` values
if you are not certain. The response `data.id` is the canonical
element ID; use it as `source_id`/`target_id` when adding
relationships and as `element_id` when adding view nodes.

Args:
    element_type: A supported ArchiMate element type, e.g.
        `BusinessActor`, `BusinessProcess`, `ApplicationComponent`,
        `ApplicationService`, `DataObject`, `Node`, `Artifact`,
        `Goal`, `Stakeholder`, `Grouping`, `AndJunction`,
        `OrJunction`. Use `list_supported_types` for the full list.
    name: Element name. Must be a non-empty string.
    description: Optional element documentation text.
    folder_path: Optional conceptual folder path. Roots are
        normalized: `Business`, `/Business`, and `business` resolve
        to `/Business`. Sub-folders such as `/Business/Actors` are
        preserved.
    properties: Optional custom property key-value pairs. Values are
        stored as strings.
    element_id: Optional stable element ID. When omitted a UUID is
        generated. Must be unique across the
        *entire* active model — not just within this call, this
        batch, or this concept type. An id already used by any
        element, relationship, view, node or connection is
        rejected. When generating ids across several batches,
        namespace them (`bp-`, `ac-`, `tech-`) so batches cannot
        collide.

Returns:
    Success envelope with `data` shaped like an `ElementDetail`:
    `{id, name, type, description, properties, folder,
    incoming_relationship_ids, outgoing_relationship_ids}`.

Errors:
    `INVALID_ELEMENT_NAME` when `name` is missing or blank.
    `InvalidElementTypeError` for an unknown `element_type`.
    `ModelNotFoundError` if no model is active.
    `ModelOperationError` for a duplicate `element_id` or invalid
    folder path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
element_idNo
propertiesNo
descriptionNo
folder_pathNo
element_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Provides extensive behavioral details beyond annotations: describes element creation behavior, folder path normalization, element_id uniqueness constraints and collision rejection, and lists all four error conditions. Annotations (readOnlyHint=false, destructiveHint=false) are consistent with the description's creation semantics.

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 description is well-structured with clear sections for args, returns, and errors, and uses bullet-like formatting for readability. It is somewhat verbose but every sentence adds value; minor redundancy in error enumeration could be streamlined.

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 6 parameters, a rich output schema (described), and no gaps in usage or error documentation, the description is fully complete. Covers purpose, parameter details, return shape, and error conditions without leaving the agent guessing.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates: it explains each parameter's purpose, constraints (e.g., name must be non-empty), examples for element_type, normalization details for folder_path, and namespace advice for element_id. This is far beyond baseline given the coverage gap.

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?

Clearly states the verb ('Add') and resource ('new ArchiMate element'), specifies the scope ('to the active model'), and distinguishes from siblings (e.g., 'add_elements' for batch, 'list_supported_types' for discovery) through explicit cross-reference.

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?

Explicitly advises using 'list_supported_types' when uncertain about element types, and explains how to use the returned ID for relationships and view nodes. However, lacks explicit when-not-to-use guidance (e.g., versus 'add_elements') and does not state the prerequisite of an active model directly, though errors hint at 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/byrondelgado/mcp-archimate'

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