staruml-mcp

Overview Schema Source Related Servers Discussions Admin

execute_command

Run built-in StarUML commands by their ID to automate tasks like saving, creating, or editing diagrams via the MCP server.

Instructions

Execute any built-in StarUML command by its ID. Use get_all_commands to discover available IDs. 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": "execute_command"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Command ID. Examples: 'project:save', 'view:fit-to-window', 'project:new'
`args`	No	Optional positional arguments passed to the command handler

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Jul 28, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. Does not disclose potential side effects, error handling, or destructive nature of some commands. Only mentions extension dependency.

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?

Three concise sentences, front-loaded with action. No unnecessary words.

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?

Given the power of this tool (executing arbitrary commands) and lack of output schema/annotations, more detail on return values, errors, and behavioral expectations is needed.

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?

Schema description coverage is 100%, so parameters are well-documented in schema. Description adds minimal value beyond that.

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 'Execute any built-in StarUML command by its ID', with a specific verb and resource. It distinguishes from siblings by referencing get_all_commands for discovering IDs.

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?

Explicitly tells when to use get_all_commands to discover available IDs and mentions the required extension. Lacks explicit 'when not to use', but context is clear.

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