Skip to main content
Glama
byrondelgado

mcp-archimate

by byrondelgado
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

connect_visible_relationships

Idempotent

Add visual connections for every relationship whose source and target nodes are visible in the view. Skips existing connections and optionally rolls back on error.

Instructions

Add visual connections for every relationship whose endpoints are visible.

Iterates over every relationship in the active model and, when both
its source and target elements are already visible nodes in the
view, adds the missing visual connection. Existing connections are
skipped.

Args:
    view_id: ID of the target view.
    detail: `summary` (default) or `full`. Every relationship that
        is not drawable in this view counts as a skip, so on a
        multi-view model the skip list is close to the whole
        relationship set and every entry is expected. `full` adds
        `data.skipped_relationship_ids`.
    rollback_on_error: When true (default), restore the previous
        view state if any connection fails.

Returns:
    Success envelope with `data.connection_ids` (newly added),
    `data.added_count`, `data.skipped_count`, and `data.detail`.
    Under `full`, also `data.skipped_relationship_ids`.

Errors:
    `ModelOperationError` when `view_id` is unknown, or for an
    unknown `detail` level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNosummary
view_idYes
rollback_on_errorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

The description details behaviors beyond annotations: existing connections are skipped, rollback_on_error mechanism, detail levels affecting response, and error conditions. This adds significant context to the idempotentHint and readOnlyHint 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 well-structured: a one-sentence summary followed by iterative logic, then clear sections for args, returns, and errors. Every sentence adds value without redundancy.

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

Completeness5/5

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

The description covers the tool's purpose, process, parameters, return values, and errors comprehensively. Given the tool's complexity and available structured data, no gaps remain.

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

Parameters5/5

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

With schema description coverage at 0%, the description fully explains each parameter: view_id (required), detail (enum-like options with effect), and rollback_on_error (default behavior). It adds meaning beyond the schema's type and default values.

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 starts with a specific verb and resource: 'Add visual connections for every relationship whose endpoints are visible.' It clearly states the tool's function and distinguishes it from sibling tools like 'add_connection_to_view' which operate on single connections.

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 explains the iterative process and when connections are skipped, providing context for use. However, it does not explicitly indicate when not to use this tool or provide comparisons to alternative siblings like 'ensure_all_relationships_in_views'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/byrondelgado/mcp-archimate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server