Skip to main content
Glama

add_note_to_view

Add a visual annotation to an ArchiMate view for comments or notes without creating model elements. Place sticky notes at any position and optionally connect them to diagram nodes.

Instructions

Add a diagram-only note (sticky annotation) to a view.

Use this to comment on a diagram — a caveat, an owner, a "retire in
FY27". Do NOT create a `Grouping` element just to write a comment:
that pollutes the model tree and participates in validation, while a
note does not.

Notes are visual only. A note has no ArchiMate element, no folder
and no model-tree entry, so it never shows up in `query_elements`,
`count_by_type`, `list_orphan_elements` or the coverage section of
`build_quality_report`. `connect_to_node_ids` draws annotation-only
connector lines that create NO ArchiMate relationship.

`x`/`y` are kept exactly as given, including across
`auto_layout_view` (both layout engines), because a note annotates
one specific spot. Layout will not move element nodes out from under
a note, so place notes in free space — off to the side of the
diagram, or below it. Routed connections are drawn around notes.

Args:
    view_id: ID of the target view.
    text: Note text. Must be non-empty; kept verbatim, so multi-line
        text keeps its line breaks and indentation. Verbatim also
        means escape sequences are NOT interpreted: pass real line
        breaks for a multi-line note, because a literal backslash-n
        is stored and rendered as those two characters.
    x: X coordinate (top-left, integer pixels). Used exactly.
    y: Y coordinate (top-left, integer pixels). Used exactly.
    width: Note width in pixels. Defaults to 185 (Archi's default).
    height: Note height in pixels. Defaults to 80.
    connect_to_node_ids: Optional list of things to point at. Each
        entry may be a visual node ID or an element ID that is
        already visible in this view.
    note_id: Optional stable visual node ID. When omitted a UUID is
        generated.

Returns:
    Success envelope with `data.node_id`, `data.connection_ids`,
    `data.connected_node_ids` (resolved visual node IDs),
    `data.text`, and the geometry `data.x`, `data.y`,
    `data.width`, `data.height`.

Errors:
    `INVALID_NOTE_TEXT` when `text` is missing or blank.
    `ViewNotFoundError` when `view_id` is unknown.
    `ModelOperationError` for a duplicate `note_id`, or for connect
        targets that are not visible in the view — the unresolved
        IDs are listed in `error.details.unknown_ids` and nothing is
        created.

Notes are not updatable or deletable yet: recreate the view (or the
note) if the text or placement needs to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes
textYes
widthNo
heightNo
note_idNo
view_idYes
connect_to_node_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description discloses key behaviors beyond annotations: notes are visual-only, not updatable/deletable, x/y preserved across layout, connect_to_node_ids creates no relationships, and errors are listed. Annotations indicate it's a write operation, and the description adds rich context.

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?

The description is well-structured with a clear opening sentence, bullet points for args, and separate sections for returns and errors. While somewhat long, every sentence adds value for the tool's complexity (8 parameters).

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 complexity (8 parameters, immutable notes, layout behavior, connection semantics), the description covers inputs, outputs, errors, and limitations comprehensively. It provides complete guidance for correct 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?

With 0% schema description coverage, the description fully compensates by explaining each parameter in detail: text verbatim handling, x/y exact usage, defaults for width/height, optional note_id, and connect_to_node_ids semantics. It adds significant meaning beyond the schema.

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 a diagram-only note, distinguishing it from Grouping elements and other tools. It uses a specific verb and resource, and explicitly contrasts with creating a Grouping for comments, which pollutes the model tree.

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 tells when to use (to comment on a diagram) and when not to (do not use Grouping). It provides context about notes being visual-only and not participating in queries. However, it does not explicitly mention alternative tools like add_node_to_view, though the sibling list implies them.

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