Skip to main content
Glama
byrondelgado

mcp-archimate

by byrondelgado
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_view

Creates a new ArchiMate view (diagram) in the active model. Specify a name, optional viewpoint from supported types, and folder path to organize views.

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). Take the
value from `list_supported_types` (`data.viewpoints`) rather than
inferring it from the viewpoint's English name — a plausible
`business_process` is not accepted, `business_process_cooperation`
is.

Args:
    name: View name. Must be a non-empty string.
    view_id: Optional stable view 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.
    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. Both catalogs are in `list_supported_types` under
        `data.viewpoints`. Invalid values are rejected before the
        view is created — nothing is left behind, so the same
        `view_id` can be reused on the retry — and the error
        carries both 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`, an unknown
    `viewpoint`, or an invalid folder path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
view_idNo
viewpointNo
propertiesNo
descriptionNo
folder_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations indicate non-read-only and non-destructive. The description details that invalid viewpoint values are rejected before creation (nothing left behind, view_id reusable), error behaviors, and the uniqueness constraint. This adds significant behavioral context beyond annotations.

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 Args, Returns, and Errors sections. While detailed, every sentence adds value. It is slightly verbose but appropriately sized for the complexity.

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 6 parameters, output schema existence, and annotations, the description is nearly complete. It covers return shape, errors, and usage context with sibling tools. No gaps in required information.

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%, but the description thoroughly explains each parameter: `name` (non-empty), `view_id` (optional, UUID, uniqueness across model), `folder_path` (normalization), `viewpoint` (from `list_supported_types`), and mentions `properties` and `description` as optional. It provides critical usage details not in 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 'Create a new ArchiMate view (diagram) in the active model.' It specifies the verb (create), resource (view), and context (active model), and distinguishes from siblings like `add_node_to_view` and `add_connection_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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: use this to create a view, then add nodes/connections with other tools. It advises obtaining viewpoint values from `list_supported_types` and warns about view_id uniqueness across the entire model, including naming conventions for batch commands.

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