Skip to main content
Glama
Sign In
staruml-mcp

staruml-mcp

by ezrabrilliant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

switch_diagram

Switch to a specific diagram in StarUML by providing its diagram ID. Use this to navigate between diagrams in your project.

Instructions

Focus (open tab) a diagram by its ID. 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": "switch_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDiagram _id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It notes the extension requirement but does not disclose potential side effects (e.g., what happens if the diagram ID is invalid, whether it triggers events, or if it affects unsaved changes). This is insufficient for a tool with no annotations.

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 two sentences: first states the purpose, second gives a critical installation requirement. No unnecessary words.

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 tool with one parameter and no output schema, the description covers purpose and a prerequisite. It lacks mention of error scenarios (e.g., missing extension or invalid ID), but overall is fairly complete given simplicity.

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 coverage is 100% (the single parameter 'id' is described as 'Diagram _id' in the schema). The description adds nothing beyond the schema, so baseline 3 is appropriate.

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 the action ('focus/open tab') and the resource ('a diagram by its ID'). It distinguishes from sibling tools like create_diagram or close_diagram, as those have different purposes.

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?

The description mentions a prerequisite (extension installation) but does not explicitly state when to use this tool versus alternatives like get_current_diagram_info or get_all_diagrams_info. Usage context is implied but not fully clarified.

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