Skip to main content
Glama

add_node_to_view

Add an ArchiMate element as a visual node in a view. Automatically places node to avoid overlaps or uses specified coordinates.

Instructions

Add an ArchiMate element as a visual node in a view.

If `x`/`y` are omitted, or the requested rectangle would overlap an
existing node, the server places the node in the next free slot.
Default node size is 160x80 (junctions are normalized to 32x32 by
`auto_layout_view`).

Args:
    view_id: ID of the target view.
    element_id: ID of the element to render in the view.
    x: Optional preferred X coordinate (top-left, integer pixels).
    y: Optional preferred Y coordinate (top-left, integer pixels).
    width: Node width in pixels. Defaults to 160.
    height: Node height in pixels. Defaults to 80.
    node_id: Optional stable visual node ID. When omitted a UUID is
        generated.

Returns:
    Success envelope with `data.node_id` containing the visual
    node's UUID.

Errors:
    `ViewNotFoundError` (returned as `ModelOperationError` from the
        manager) when `view_id` is unknown.
    `ElementNotFoundError` when `element_id` is unknown.
    `ModelOperationError` for a duplicate `node_id`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
widthNo
heightNo
node_idNo
view_idYes
element_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description goes beyond annotations (non-readonly, non-destructive) by detailing placement behavior on overlap, default node sizing, and junction normalization. It also lists specific error conditions, offering rich 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 concise with a clear summary, structured parameter list, and separate returns/errors sections. Every sentence adds value without redundancy.

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 7 parameters, no schema descriptions, but an existing output schema, the description fully covers inputs, behavioral nuances, errors, and return structure, making it complete for selection and invocation.

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 description coverage, the description's 'Args' block explains all 7 parameters, including behaviors for omitted coordinates, default sizes, and optional node_id generation, adding meaning the schema lacks.

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 an ArchiMate element as a visual node in a view.' It specifies the verb (add) and distinct resource (element to node), distinguishing it from sibling tools like add_note_to_view or add_connections_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 explains when to use coordinate parameters and how server handles omissions or overlaps, providing context on default sizes and auto_layout normalization. However, it does not explicitly exclude alternatives or state when not to use this tool.

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