Skip to main content
Glama

add_connections_to_view

Add multiple visual connections to an ArchiMate view in a single call, with automatic rollback on failure.

Instructions

Add multiple visual connections to a view in one call.

Each connection item supports the same fields as
`add_connection_to_view`. Both short and long field names are
accepted (`relationship` or `relationship_id`, `id` or
`connection_id`).

Connection item shape:
    ```
    {
      "id": "id-uses-conn",          # optional stable ref
      "relationship": "id-uses"      # required (alias: relationship_id)
    }
    ```

Args:
    view_id: ID of the target view.
    connections: List of connection item objects.
    rollback_on_error: When true (default), restore the previous
        view state if any item fails.

Returns:
    Success envelope with `data.connection_ids`, `data.count`, and
    `data.rollback_on_error`.

Errors:
    `ModelOperationError` and `RelationshipNotFoundError` for the
    first failing item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
view_idYes
connectionsYes
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?

Beyond annotations (which already indicate non-read-only, non-destructive), the description adds critical behavioral details: rollback_on_error behavior, return envelope structure, and error types. No contradiction with annotations.

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 sections for purpose, connection item details, Args, Returns, and Errors. Every sentence adds value, and it is front-loaded with the core action.

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 the tool's moderate complexity (3 parameters, output schema exists), the description covers all essential aspects: input, return fields, and error conditions. The presence of an output schema reduces the need for detailed return documentation, but the description provides it anyway.

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?

The input schema has no descriptions (0% coverage), but the description fully explains each parameter, including the complex 'connections' item shape, default value and effect of rollback_on_error, and the syntax for field aliases.

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 visual connections to a view, using a specific verb ('Add') and resource ('visual connections to a view'), distinguishing it from the sibling add_connection_to_view.

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 the sibling add_connection_to_view by stating that each connection item supports the same fields, implying batch vs single usage. However, it lacks explicit 'when to use' or 'when not to use' guidance, though the context is clear.

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