Skip to main content
Glama
byrondelgado

mcp-archimate

by byrondelgado
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

connect_visible_relationships

Idempotent

Automatically add missing visual connections for relationships whose source and target elements are already visible in a view. New connections are added while existing ones are skipped.

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.
    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_relationship_ids`, and
    `data.skipped_count`.

Errors:
    `ModelOperationError` when `view_id` is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
view_idYes
rollback_on_errorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Adds context beyond annotations: explains idempotency (skipping existing), rollback behavior, error conditions, and return data structure. No contradiction with 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?

Well-structured with separate sections for purpose, 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?

Given the presence of an output schema and two parameters, the description covers all necessary aspects: operation, parameters, return values, and error types. No gaps.

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?

Both parameters are explained in the Args section with clear semantics and default behavior, compensating fully for the 0% schema description coverage.

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?

Clear verb-resource combination ('Add visual connections') with specific condition ('endpoints are visible'). Distinguishes from sibling tools like add_connection_to_view by emphasizing bulk operation over all relationships with visible endpoints.

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?

Describes what the tool does but does not explicitly tell when to use it over alternatives like add_connections_to_view or ensure_all_relationships_in_views. No when-not guidance.

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