mcp-archimate

Overview Schema Source Related Servers Discussions Admin

delete_element

Destructive

Remove an ArchiMate element from the active model. Automatically deletes related relationships and visual nodes to keep the model consistent.

Instructions

Delete an ArchiMate element from the active model.

pyArchimate also removes dependent concepts such as relationships
and visual nodes/connections referencing the deleted element.

Args:
    element_id: ID of the element to delete.

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

Errors:
    `ElementNotFoundError` when `element_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": {
      "element_id": "<element_id>"
    },
    "name": "delete_element"
  }
}

Input Schema

Name	Required	Description	Default
`element_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=false. The description adds value by detailing that pyArchimate removes dependent concepts, providing behavioral context beyond the structured fields.

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?

The description is concise with clear sections (Args, Returns, Errors). The first sentence immediately states the purpose, and 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?

For a simple one-parameter tool with annotations and an output schema present, the description fully covers the operation: deletion, cascade effects, and error conditions. It is complete and sufficient.

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?

With 0% schema description coverage, the description provides minimal extra meaning: 'element_id: ID of the element to delete.' This is adequate but does not elaborate on format or other constraints, earning a baseline score of 3.

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 deletes an ArchiMate element from the active model, using a specific verb and resource. It distinguishes itself from sibling tools like delete_relationship and delete_view by focusing on elements.

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 explains it removes dependent concepts (relationships, visual nodes), indicating it is the comprehensive delete for elements. It does not explicitly state when to use alternatives like delete_relationship, but the context implies appropriate usage.

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

Deploy Server