staruml-mcp

Overview Schema Source Related Servers Discussions Admin

open_project

Opens a StarUML project file (.mdj) to load an existing UML project for editing and analysis.

Instructions

Open a StarUML project file (.mdj). 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": {
      "filename": "<filename>"
    },
    "name": "open_project"
  }
}

Input Schema

Name	Required	Description	Default
`filename`	Yes	Absolute path to the .mdj project file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Jul 28, 2026

TDQS

B3.4/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. Only discloses extension dependency, but omits side effects, error behavior, or state changes (e.g., whether current project is replaced).

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?

Two concise sentences: purpose and prerequisite. No fluff, but slightly under-specified for behavioral context.

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

Completeness3/5

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

Adequate for a simple open command with one required parameter and no output schema. Covers purpose and requirement, but lacks success/failure behavior or state impact information.

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?

Single parameter 'filename' is fully described in schema ('Absolute path to the .mdj project file'). Description adds no extra meaning beyond schema, meeting baseline for 100% coverage.

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 'Open a StarUML project file (.mdj).' with specific verb and resource. Distinguishes from siblings like new_project or save_project.

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 prerequisite extension and provides installation link, but does not explicitly differentiate from alternative tools or provide when-not-to-use guidance.

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