Skip to main content
Glama

add_connection_to_view

Add a visual connection for a relationship in an ArchiMate view. Requires both endpoint nodes to already be in the view.

Instructions

Add a visual connection for a relationship in a view.

Both endpoint elements of the relationship must already be visible
as nodes in the view. Use `add_node_to_view` to add missing
endpoints first, or call `connect_visible_relationships` to draw
every relationship whose endpoints are already visible.

Args:
    view_id: ID of the target view.
    relationship_id: ID of the relationship to render.
    connection_id: Optional stable visual connection ID. When
        omitted a UUID is generated.

Returns:
    Success envelope with `data.connection_id` containing the
    visual connection UUID.

Errors:
    `ModelOperationError` when `view_id` is unknown, when either
        endpoint node is not present in the view, or when
        `connection_id` is duplicated.
    `RelationshipNotFoundError` when `relationship_id` is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
view_idYes
connection_idNo
relationship_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Describes effect (adds visual connection), optional connection_id with UUID generation, and lists specific errors (ModelOperationError, RelationshipNotFoundError). 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?

Well-structured with Args, Returns, Errors sections. Concise and comprehensive with no wasted sentences.

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?

Covers all aspects: purpose, prerequisites, parameters, return value, errors. Output schema exists and description supplements it appropriately.

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?

Despite 0% schema coverage, describes each parameter: view_id (target view), relationship_id (relationship to render), connection_id (optional stable ID). Also explains return value and errors.

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 'Add a visual connection for a relationship in a view', specifying verb, resource, and context. Distinguishes from sibling tools like 'add_node_to_view' and 'connect_visible_relationships'.

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 says when to use: both endpoints must be visible. Provides alternatives: add_node_to_view for missing endpoints, or connect_visible_relationships for all visible relationships.

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