Skip to main content
Glama

add_relationship

Create a new ArchiMate relationship between existing elements by providing source ID, target ID, and relationship type. Optionally add name, description, properties, access type, or influence strength.

Instructions

Add a new ArchiMate relationship between two elements.

Both endpoints must already exist as elements in the active model.
Use `list_supported_types` to discover valid `relationship_type`,
`access_type`, and `influence_strength` values.

Args:
    relationship_type: A supported pyArchimate relationship type,
        without the `Relationship` suffix. Examples: `Assignment`,
        `Serving`, `Composition`, `Aggregation`, `Realization`,
        `Triggering`, `Flow`, `Access`, `Influence`,
        `Specialization`, `Association`. Note: Archi's "Used By"
        concept maps to `Serving`.
    source_id: ID of the source element.
    target_id: ID of the target element.
    name: Optional relationship name.
    description: Optional documentation text.
    properties: Optional custom property key-value pairs (string
        values).
    access_type: Required only for `Access` relationships. One of
        `Access`, `Read`, `Write`, `ReadWrite`.
    influence_strength: Required only for `Influence` relationships.
        One of `+`, `++`, `-`, `--`, or `0`-`10`.
    relationship_id: Optional stable relationship 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 a `RelationshipDetail`:
    `{id, name, type, description, properties, access_type,
    influence_strength, source_element_id, target_element_id}`.

Errors:
    `InvalidRelationshipTypeError` for an unknown
        `relationship_type`.
    `ElementNotFoundError` when `source_id` or `target_id` is
        unknown.
    `ModelNotFoundError` if no model is active.
    `ModelOperationError` for invalid relationship combinations,
        duplicate `relationship_id`, or unsupported access/influence
        values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
source_idYes
target_idYes
propertiesNo
access_typeNo
descriptionNo
is_directedNo
relationship_idNo
relationship_typeYes
influence_strengthNo
semantic_validationNowarn

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and the description adds context: relationship_id uniqueness across entire model, conditional required parameters, and error types. No contradiction.

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 Args, Returns, Errors sections; front-loaded with core purpose. Slightly lengthy but every sentence adds value; could be tightened slightly.

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?

For a complex tool with 11 parameters and no schema descriptions, the description covers preconditions, parameter semantics, error cases, and return shape. Output schema exists, so return values are documented. Complete for agent use.

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%, so description fully compensates by explaining each parameter with examples, conditional requirements (access_type for Access, influence_strength for Influence), and uniqueness constraint for relationship_id.

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 'Add a new ArchiMate relationship between two elements,' specifying the verb and resource. It distinguishes from sibling tools like add_relationships (bulk) and update_relationship.

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 states that both endpoints must already exist and references list_supported_types for valid values. Does not explicitly state when not to use or mention alternatives, but preconditions are 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