Skip to main content
Glama
Sign In
MCP ArchiMate Server

MCP ArchiMate Server

by dqxorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

design_from_document

Generate an ArchiMate model from a markdown document. Converts architecture descriptions into structured ArchiMate elements and relationships.

Instructions

Generate ArchiMate model from an architecture markdown document

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": {
      "document_path": "<document_path>"
    },
    "name": "design_from_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_pathYesPath to architecture markdown file
scopeNoDesign scope

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.2/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. The description implies a generative action but does not disclose side effects (e.g., whether it overwrites an existing model, permissions needed, or output format). For a model generation tool, more transparency is expected.

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 a single sentence with no unnecessary words. It is concise and front-loaded, efficiently stating the purpose.

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?

Given the complexity of generating a model from a document, the description lacks completeness. There is no output schema, and no mention of what happens to the existing model, file format requirements, or the difference between 'full' and 'outline' scope. More details would improve completeness.

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% with clear parameter descriptions. The description does not add extra meaning beyond the schema, but since coverage is high, a baseline 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 'Generate ArchiMate model from an architecture markdown document', which is a specific verb (Generate) and resource (ArchiMate model). It distinguishes itself from sibling tools that focus on creating individual elements or diagrams.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or context. Given the variety of sibling tools, some indication of when to generate a model from a document vs. other actions would be helpful.

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