staruml-mcp

Overview Schema Source Related Servers Discussions Admin

delete_element

Delete a UML element from your StarUML project by providing its unique ID. Removes the specified element from the model.

Instructions

Delete an element from the project. Requires staruml-mcp-extension to be installed in StarUML. Install from https://github.com/ezrabrilliant/staruml-mcp-extension

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": {
      "id": "<id>"
    },
    "name": "delete_element"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Element _id to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Jul 28, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It correctly states the delete action, implying destructiveness, and notes the installation requirement. Missing critical details: irreversibility, impact on diagrams/relationships, permissions needed, or error conditions.

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?

Three sentences: purpose, requirement, link. No fluff. However, the requirement could be integrated at the end of the first sentence for better front-loading. Still efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a delete operation with no annotations and no output schema, the description is incomplete. Missing behavioral context like side effects (e.g., cascading deletion to child elements), irreversibility warning, and required state. A user/agent needs more to safely invoke this tool.

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?

Only one parameter 'id' with schema description 'Element _id to delete'. Schema coverage is 100%, so baseline is 3. Description adds no extra meaning beyond schema; no format or source guidance for the id. Meets but does not exceed expectations.

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?

Description clearly states the action: 'Delete an element from the project.' This is a specific verb+resource pair. It differentiates from sibling tools like 'create_element' and 'update_element' by focusing on deletion.

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?

Mentions a prerequisite (requires staruml-mcp-extension installation), which guides usage context. However, it does not provide explicit when-to-use/when-not-to-use guidance or compare with alternatives like 'update_element'. No exclusion criteria.

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