Skip to main content
Glama
Sign In
MCP ArchiMate Server

MCP ArchiMate Server

by dqxorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_relationship

Add an ArchiMate relationship between two elements by specifying the source ID, target ID, and relationship type, with optional documentation.

Instructions

Create a new ArchiMate relationship between two elements

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": {
      "relationship_type": "<relationship_type>",
      "source_element_id": "<source_element_id>",
      "target_element_id": "<target_element_id>"
    },
    "name": "create_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
relationship_typeYesRelationship type
source_element_idYesSource element ID
target_element_idYesTarget element ID
documentationNoRelationship documentation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Create', implying a write operation, but provides no details on side effects, validation, or required permissions. The agent lacks critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that immediately conveys the action. However, it could be slightly more informative without becoming verbose.

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

Completeness2/5

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

The tool is moderately complex with 4 parameters, no output schema, and no annotations. The description fails to mention whether source/target elements must exist, relationship type constraints, or success behavior, leaving significant gaps for an agent.

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 description coverage is 100%, so baseline is 3. The description adds no parameter-specific information beyond what the schema already provides (e.g., no explanation of relationship_type values or element ID format).

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 tool creates an ArchiMate relationship between two elements, using a specific verb and resource. This distinguishes it from sibling tools like create_element (creates elements) and list_relationship_types (lists types).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is provided. The description does not mention prerequisites such as element existence or relationship type validity, nor does it reference alternative tools for similar tasks.

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