Skip to main content
Glama

render_view_to_svg_file

Idempotent

Generate an SVG file from a view so it can be seen without opening Archi, for layout checks or document inclusion.

Instructions

Render one view to an SVG file so a human can look at the diagram.

Use this when someone wants to *see* a view without opening Archi —
to check that a layout reads well, or to drop a picture into a
document or chat. Lay the view out first with `auto_layout_view` if
the geometry needs work: rendering never moves anything.

SVG is a rendering, NOT a third model format. It cannot be imported
back into Archi and it is not a substitute for
`export_model_to_file` (`archi` = Archi native `.archimate`,
`archimate` = Open Group exchange XML). Use those to persist a
model; use this to look at one view.

The markup is written to disk and never returned: an 11-element view
is already ~3.2k tokens of SVG text, and reading it back would not
tell you anything you cannot get from `summarize_view` or
`build_quality_report`. Hand the returned path to the user.

Args:
    view_id: ID of the view to render.
    path: Output path on the MCP server's filesystem (`.svg`
        conventionally). `~` is expanded, relative paths resolve
        against the server's CWD, and parent directories are
        created if missing.

Returns:
    Success envelope with `data.path`, `data.view_id`,
    `data.view_name`, `data.model_name`, `data.bytes_written`,
    `data.node_count`, `data.connection_count`, and the rendered
    canvas size in `data.width` / `data.height`. Never the markup.

Errors:
    `ModelNotFoundError` if no model is active.
    `ViewNotFoundError` when `view_id` is unknown.
    `ModelOperationError` for a blank path or a write failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
view_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description adds significant behavior beyond annotations: 'rendering never moves anything', 'SVG is a rendering, NOT a third model format', and 'The markup is written to disk and never returned.' It also explains token size to justify not returning the SVG, and clarifys file creation behavior (expanding ~, creating parent dirs). No contradictions 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?

The description is well-structured with a clear summary first, then usage details, parameter explanations, return value list, and error cases. Every sentence adds value, and there is no redundancy or 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 the tool's complexity (file system handling, return data, error conditions, sibling differentiation), the description is fully complete. It covers all necessary context: when to use, what the output is, how parameters work, what returns and errors occur, and how it differs from related 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?

Schema description coverage is 0%, but the description fully compensates: 'view_id: ID of the view to render.' and 'path: Output path on the MCP server's filesystem (.svg conventionally). `~` is expanded, relative paths resolve against the server's CWD, and parent directories are created if missing.' This adds crucial meaning beyond the schema.

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 'Render one view to an SVG file so a human can look at the diagram,' providing a specific verb and resource. It also distinguishes from siblings like export_model_to_file and auto_layout_view by clarifying that SVG is not a model format and cannot be imported back.

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?

Explicit guidance on when to use (to check layout, drop into document/chat) and when not to use (not a substitute for export_model_to_file). It also recommends using auto_layout_view first if layout needs work, providing a clear alternative.

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