Skip to main content
Glama
Sign In
staruml-mcp

staruml-mcp

by ezrabrilliant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

save_project

Save the current StarUML project to its existing path or optionally to a specified absolute file path.

Instructions

Save the current StarUML project. If filename is given, saves to that path. Otherwise saves to current path. Requires staruml-mcp-extension to be installed in StarUML. Install from https://github.com/ezrabrilliant/staruml-mcp-extension

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoOptional absolute path. If omitted, saves to current project path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It explains the basic behavior (saving to path or current path) and the installation requirement, but does not disclose whether the operation overwrites existing files, returns success/failure, or has other side effects.

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 sentences with no waste. First sentence states purpose, second clarifies behavior, third gives prerequisite. Information is front-loaded and every sentence earns its place.

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?

For a simple save tool with one optional param and no output schema, the description covers the essential behavior and prerequisite. Minor omission: no mention of return value or success indicators, but not critical given simplicity.

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

Parameters4/5

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

Schema coverage is 100% (one parameter 'filename'). The description adds meaning by explaining it is optional, an absolute path, and that omitting it saves to current project path. This goes beyond the schema's description.

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 'Save the current StarUML project' with specific verb and resource. It further distinguishes behavior when filename is given vs omitted, differentiating from siblings like save_project_as.

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 explicitly mentions a prerequisite: requires the staruml-mcp-extension to be installed, with an install link. It does not explicitly list when not to use it or compare to alternatives, but the filename parameter and sibling names imply the distinction.

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