Skip to main content
Glama

add_elements

Add multiple elements to the active model in one call, supporting rollback on error to restore previous state if any item fails.

Instructions

Add multiple elements to the active model in one call.

Each element item supports the same fields as `add_element`. Both
short and long field names are accepted (`type` or `element_type`,
`id` or `element_id`).

Element item shape:
    ```
    {
      "id": "id-customer",        # optional stable ref
      "name": "Customer",          # required
      "type": "BusinessActor",     # required (alias: element_type)
      "description": "...",       # optional
      "folder_path": "/Business", # optional
      "properties": {"k": "v"}     # optional
    }
    ```

Args:
    elements: List of element item objects.
    rollback_on_error: When true (default), restore the previous
        model state if any item fails. Set to false to keep partial
        results.

Returns:
    Success envelope with `data.elements` (list of `ElementDetail`),
    `data.count`, and `data.rollback_on_error`.

Errors:
    `ModelNotFoundError`, `InvalidElementTypeError`,
    `ModelOperationError` for the first failing item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementsYes
rollback_on_errorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations are consistent (readOnlyHint=false, destructiveHint=false). The description goes beyond by detailing rollback behavior, error types (ModelNotFoundError, etc.), and that field aliases are accepted. This provides clear behavioral context.

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 well-structured with a summary, parameter details, returns, and errors. It is concise, uses a code block for clarity, and every sentence adds value.

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?

The tool is a batch variant; the description covers input shape, rollback behavior, errors, and return structure. Combined with sibling context and output schema existence, it provides complete guidance.

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?

Schema coverage is 0%, but the description fully explains both parameters: elements includes a documented shape with field examples, and rollback_on_error is described with default and effect. This compensates entirely.

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 adds multiple elements to the active model, distinguishing it from the singular add_element sibling. It specifies the scope ('to the active model') and provides a concrete example of element shape.

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 implies use for bulk addition, and the rollback_on_error parameter offers guidance on error handling. However, it does not explicitly contrast with alternatives like add_element or provide when-not-to-use scenarios.

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