Skip to main content
Glama
byrondelgado

mcp-archimate

by byrondelgado
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

update_view

Idempotent

Update an existing view's metadata fields like name, description, or properties. Optionally change viewpoint with validation to prevent errors.

Instructions

Update an existing ArchiMate view.

Only metadata fields can be updated; nodes and connections are
managed by `add_node_to_view`, `add_connection_to_view`, and the
layout tools.

Args:
    view_id: ID of the view to update.
    updates: Mapping of fields to update. Supported keys:
        - `name` (str): New view name.
        - `description` (str): New documentation text.
        - `properties` (dict[str, str]): Property updates merged
          into existing properties.
    viewpoint: Optional viewpoint, as on `create_view`. Validated
        before anything is applied: an unknown value leaves the
        view completely untouched, `name` and `description`
        included.

Returns:
    Success envelope with the updated `ViewDetail` in `data`.

Errors:
    `ViewNotFoundError` when `view_id` is unknown.
    `ModelOperationError` for an unknown `viewpoint`, with both
    accepted catalogs in `error.details`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYes
view_idYes
viewpointNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.8/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true. Description adds that viewpoint validation prevents partial updates, specifying that unknown viewpoint leaves view untouched. Provides error handling details.

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?

Efficiently structured with a clear purpose statement, constraints, then Args/Returns/Errors sections. Every sentence adds value; no wasted words.

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?

Combined with annotations and output schema, the description fully covers tool purpose, constraints, parameters, return, and errors, enabling correct agent 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?

Schema coverage is 0%, but description thoroughly documents all parameters: view_id, updates (with supported keys and merge behavior for properties), and viewpoint (validation, default null).

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?

Clearly states 'Update an existing ArchiMate view' and explicitly distinguishes itself from sibling tools like add_node_to_view and add_connection_to_view by noting that nodes and connections are managed elsewhere.

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?

Provides explicit when-to-use (metadata updates) and when-not-to-use (nodes/connections), names specific alternatives, and explains viewpoint validation behavior.

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