staruml-mcp

Overview Schema Source Related Servers Discussions Admin

get_element_by_id

Retrieve a StarUML model element using its internal ID. Requires the staruml-mcp-extension installed.

Instructions

Retrieve a model element by its internal 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": "get_element_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Element _id as stored in the StarUML repository

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Jul 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves an element, which implies a read-only operation, but does not disclose behavior on missing IDs, error conditions, or any side effects. The prerequisite mention adds some transparency.

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, consisting of two sentences. The first sentence front-loads the purpose, and the second sentence adds a critical prerequisite. No unnecessary words or repetition.

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?

Given the tool's simplicity (one parameter, no output schema, read-only), the description covers the essential purpose and a key prerequisite. It could be enhanced by mentioning the return type or behavior on invalid IDs, but it is largely complete for its 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?

The input schema provides 100% coverage with a description for the required 'id' parameter: 'Element _id as stored in the StarUML repository'. The tool description does not add additional meaning beyond the schema, so baseline score of 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 'Retrieve a model element by its internal ID', providing a specific verb (Retrieve) and resource (model element). This clearly distinguishes it from siblings like find_elements (which searches by criteria) or get_diagram_image_by_id (different resource type).

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 ('Requires staruml-mcp-extension to be installed') and provides an installation link, but does not provide guidance on when to use this tool versus alternatives like find_elements. The usage context is implied by the purpose but not explicitly stated.

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