Skip to main content
Glama
Sign In
StarUML MCP Server

StarUML MCP Server

Official
by staruml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_current_diagram_info

Retrieve details about the active diagram in StarUML, including its elements and structure, to support diagram inspection and code generation.

Instructions

Get information for the current diagram in StarUML.

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": "get_current_diagram_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Get information', which implies a read-only operation, but it does not disclose return format, possible failure modes (e.g., no current diagram open), or any other behavioral details beyond the tool's name.

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?

One concise sentence, front-loaded with the action and resource. No wasted words.

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?

For a tool with no parameters, annotations, or output schema, the description is minimally adequate. It clarifies the target ('current diagram in StarUML') but leaves the returned information undefined, which is a notable gap given no output schema exists.

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?

The tool has zero parameters, so there is no parameter semantic burden. Baseline for 0-parameter tools is 4; the description correctly avoids inventing parameter details.

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 uses a specific verb ('Get') and identifies the resource ('information for the current diagram in StarUML'). The term 'current' distinguishes it from siblings like get_all_diagrams_info (all diagrams) and get_diagram_image_by_id (image by ID), while generate_diagram clearly has a different action.

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 implies when to use the tool (when information about the current diagram is needed) but does not explicitly state alternatives or exclusions. It does not mention that get_all_diagrams_info should be used for a list of all diagrams, though the sibling names make this inferable.

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