Skip to main content
Glama
Sign In
mcp-archimate

mcp-archimate

by byrondelgado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_view

Destructive

Delete an ArchiMate view and its visual nodes and connections from the active model without removing the underlying elements or relationships. Provide the view ID to delete.

Instructions

Delete an ArchiMate view from the active model.

Removes the view and its visual nodes/connections. Underlying
elements and relationships are NOT removed.

Args:
    view_id: ID of the view to delete.

Returns:
    Success envelope with `data.deleted=true`.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "view_id": "<view_id>"
    },
    "name": "delete_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
view_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds context by detailing that the view and its visual components are removed while underlying elements/relationships are preserved, which exceeds the annotation information.

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 concise and well-structured with labeled sections (Args, Returns, Errors). Every sentence adds value, and there is no unnecessary fluff. Could potentially be slightly shorter, but current length is justified.

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?

The description covers the main behavioral aspects: deletion scope, return value, and error condition. Given the presence of an output schema (implied by 'Success envelope'), the description is complete enough for an agent to understand the tool's effect.

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

Parameters3/5

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

The schema has 0% description coverage, so the description must compensate. The Args section describes view_id as 'ID of the view to delete', which adds basic meaning but no additional constraints or format details. This is adequate for a single string 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 'Delete an ArchiMate view from the active model' and specifies what is removed (view and visual nodes/connections) and what is NOT removed (underlying elements and relationships). This distinguishes it from sibling tools like delete_element and delete_relationship.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for deleting views but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. The context is clear from the tool name and sibling list, but no direct guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools