Skip to main content
Glama

create_empty_model

Destructive

Creates a new empty ArchiMate model and sets it as the active model. Required before adding elements, relationships, or views; replaces any existing active model.

Instructions

Create a new empty ArchiMate model and make it the active model.

Replaces any currently active model. Call this (or one of the
`load_model_*` tools) before any element/relationship/view tool.
Use `update_model` to change this metadata later, including on a
model that was loaded rather than created.

Args:
    name: Human-readable model name. Must be a non-empty string.
    description: Optional model-level documentation. Comes back as
        `data.model_info.documentation` and survives both export
        formats.
    properties: Optional model-level properties. Keys and values are
        coerced to strings.

Returns:
    Success envelope with `data.model_id` (the new model UUID) and
    `data.model_info` (same shape as `pyarchimate://activemodel/info`:
    name, id, documentation, properties, elements_count,
    relationships_count, views_count, is_loaded).

Errors:
    `INVALID_MODEL_NAME` when `name` is missing or blank.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
propertiesNo
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations provide destructiveHint but the description goes further: it details the replacement behavior, return envelope structure (`data.model_id`, `data.model_info`), error conditions (`INVALID_MODEL_NAME`), and parameter effects. No contradictions.

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: purpose paragraph, then Args/Returns/Errors sections. Front-loaded with the core action. Every sentence adds unique value; no redundant or vague statements.

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 tool's complexity (3 params, destructive, output schema not provided), the description covers all necessary aspects: parameters, return shape, errors, usage context, and relation to sibling tools. No missing information.

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?

Schema coverage is 0%, so description must carry full burden. It comprehensively describes all 3 parameters: name (non-empty string), description (optional, comes back as documentation), properties (optional, keys/values coerced to strings). No gaps.

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 what the tool does: 'Create a new empty ArchiMate model and make it the active model.' It distinguishes from sibling tools by explicitly referencing `load_model_*` tools and `update_model`, creating a clear usage boundary.

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

Usage Guidelines5/5

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

It explicitly states when to call: 'before any element/relationship/view tool', and provides alternatives for different tasks. It also notes that `update_model` should be used for later metadata changes.

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