Skip to main content
Glama
Sign In
mcp-archimate

mcp-archimate

by byrondelgado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_elements_to_csv

Read-only

Export all active ArchiMate model elements to a CSV string including id, name, type, description, and custom properties.

Instructions

Export all active model elements as a CSV string.

The CSV includes base columns `id`, `name`, `type`, `description`.
Custom properties are emitted as `Property:<name>` columns.

Returns:
    Success envelope with `data.csv_data` containing the CSV string.

Errors:
    `ModelNotFoundError` if no model is active.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_elements_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true. The description adds value by detailing the CSV format (base columns and custom properties as 'Property:' columns) and the error case 'ModelNotFoundError'. However, it does not disclose potential performance implications or any limits.

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 short and well-structured. It starts with the primary purpose, then details the output columns, and ends with return format and error. Every sentence is informative with no waste.

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

Completeness4/5

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

Given no parameters and an output schema, the description covers the CSV content, return envelope, and a relevant error. It could mention if the export is limited by model size or if there are any side effects, but overall it is sufficiently complete for a simple read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so schema coverage is trivially 100%. The description does not need to add parameter information, meeting the baseline expectation for no-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Export all active model elements as a CSV string', specifying the verb and resource. It distinguishes from siblings like 'export_model_content' and 'export_relationships_to_csv' by focusing on elements, but does not explicitly differentiate.

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 mentions an error case but provides no guidance on when to use this tool versus alternatives like 'export_model_content' or 'export_relationships_to_csv'. No when-not-to-use or prerequisites are stated.

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