Skip to main content
Glama

load_model_from_file

Destructive

Load an ArchiMate model from a local file, replacing the active model, and optionally inspect its structure, types, and validation status.

Instructions

Load an ArchiMate model from a local file (replaces active model).

The preferred entry point when the user gives a local `.archimate`
or XML file path. Expects a filesystem path readable by the MCP
server process; for raw XML text use `load_model_from_content`.
By default the response includes a compact inspection (summary,
type counts, validation status, recommended next calls) so a
separate `inspect_active_model` round trip is unnecessary.

Args:
    path: Local filesystem path readable by the MCP server process.
        `~` is expanded; relative paths resolve against the server CWD.
    content_format: One of `archi` (default, Archi native
        `.archimate`), `archimate` (Open Group exchange XML), or
        `xml`.
    inspect_after_load: When true (default), include a compact model
        summary, type counts, validation status, and recommended next
        calls in the response.
    include_semantic_validation: When true (default), include a
        compact semantic validation summary when inspecting.
    sample_limit: Maximum number of issue/orphan examples to include
        in compact summaries. Clamped to 0-50.

Returns:
    Success envelope with `data.model_info`, `data.loaded_from`, and
    optionally `data.inspection`.

Errors:
    `INVALID_PATH`, `FILE_NOT_FOUND`, `FILE_READ_ERROR`,
    `UnsupportedFormatError`, or `ModelOperationError`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
sample_limitNo
content_formatNoarchi
inspect_after_loadNo
include_semantic_validationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations declare destructiveHint=true, and description reinforces 'replaces active model'. Additionally, it details file path behavior, format expectations, error types, and response structure.

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 main description, Args, Returns, Errors sections. Front-loaded with purpose, every sentence adds value, no wasted words.

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 complexity (loading, optional inspection, multiple formats, errors) and presence of output schema, description covers all aspects: inputs, outputs, errors, and distinguishes from 40+ sibling tools.

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?

Input schema has 5 parameters with 0% description coverage, but description fully explains each: path (tilde expansion, relative resolution), content_format (enumeration of formats), inspect_after_load (default true, compact summary), include_semantic_validation (default true), sample_limit (clamped 0-50).

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?

Description uses specific verb 'Load' with resource 'ArchiMate model from a local file' and explicitly states it replaces the active model. It distinguishes from sibling 'load_model_from_content' for raw XML, making purpose unambiguous.

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?

Explicitly states preferred entry point for local .archimate or XML files, advises alternative for raw text, and explains that default inspection avoids extra round trips.

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