Skip to main content
Glama

create_view

Create an ArchiMate view (diagram) in the active model. Provide a name, and optionally set the viewpoint, folder path, or view ID.

Instructions

Create a new ArchiMate view (diagram) in the active model.

Views are containers for visual nodes and connections. Add nodes
with `add_node_to_view` and connections with
`add_connection_to_view` once both endpoint elements are visible.
Set a `viewpoint` so the view opens with the right Archi viewpoint
(e.g. `layered` for mixed-layer overviews, `capability` for
capability maps, `service_realization` for service views).

Args:
    name: View name. Must be a non-empty string.
    view_id: Optional stable view ID. When omitted a UUID is
        generated.
    folder_path: Optional folder path. The `Views` root is
        normalized: `Views`, `/Views`, and `views` resolve to
        `/Views`.
    viewpoint: Optional viewpoint: any canonical Archi viewpoint id
        (e.g. `layered`, `application_cooperation`) or pyArchimate
        slug. Invalid values fail with the accepted catalogs in
        `error.details`.

Returns:
    Success envelope with `data` shaped like a `ViewDetail`:
    `{id, name, nodes: [], connections: []}`.

Errors:
    `INVALID_VIEW_NAME` when `name` is missing or blank.
    `ModelNotFoundError` if no model is active.
    `ModelOperationError` for a duplicate `view_id` or invalid
    folder path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
view_idNo
viewpointNo
propertiesNo
descriptionNo
folder_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already indicate a non-destructive write (readOnlyHint=false, destructiveHint=false). The description adds error details and folder path normalization but does not reveal behavioral traits beyond what annotations imply.

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 summary, paragraphs, Args, Returns, and Errors sections. It is appropriately sized but could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and explains the return shape, the description is fairly complete. It covers errors, workflow, and most parameters, but omits the properties and description parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description explains 4 of 6 parameters (name, view_id, folder_path, viewpoint) with concrete details like validation and normalization. Missing properties and description parameters.

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 it creates a new ArchiMate view (diagram) in the active model. It distinguishes from siblings like add_node_to_view (which adds nodes to an existing view) and implies the tool is for creation, not modification.

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 provides context on when to use it (to create a view) and mentions companion tools for adding nodes and connections. However, it does not explicitly exclude use cases or compare with update_view, leaving some ambiguity.

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