Skip to main content
Glama

update_view

Idempotent

Update the name, description, and properties of an existing ArchiMate view by providing its view ID and the fields to change.

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.

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

Errors:
    `ViewNotFoundError` when `view_id` is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYes
view_idYes
viewpointNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate non-read-only, non-destructive, and idempotent behavior. The description adds valuable context about what fields are updatable and what is not (nodes/connections), but no major behavioral disclosure 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with clear sections (description, args, returns, errors). 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 the presence of an output schema and sibling tools, the description covers parameter details, return envelope, and error conditions adequately for the tool's complexity.

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 fully compensates by explaining view_id as the ID, updates as a mapping with specific supported keys (name, description, properties) and behaviour. Provides clear semantics for each parameter.

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 'Update an existing ArchiMate view' and immediately clarifies that only metadata fields can be updated, distinguishing it from sibling tools that manage nodes and connections.

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?

Explicitly specifies that only metadata fields are updated and lists sibling tools for node/connection management. Also details supported keys and errors, providing clear guidance on when 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