Aevia

Import product system

lca_import_system

Idempotent

Import an engine product system (e<N>) into a workspace as a saved system. The e<N> from engine_search is imported from its own database; the saved copy gets a stable s<N>. Captures the system's full definition server-side (no need to read its graph) and mirrors it — the copy tracks the engine original for drift and is immediately assessable (lca_run_assessment s<N>) and comparable. Idempotent: re-importing the same engine system returns the existing s<N>. Only accepts e<N> (engine systems) — a workspace s<N> is already imported, and a process p<N> is not a system. To RESTRUCTURE it: read lca_get(ref='s<N>', form='authored'), then either targeted lca_edit_linked ops (add_link/remove_link/rewire_link/replace_provider/set_target_amount/set_title — a new version of the same s<N>) or lca_compose_linked (a new s<M> from the restructured topology). The mirror stays fully assessable/comparable. On this rail lca_edit_linked also needs the base_version_seq lca_get reports.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	Yes	Engine product-system ref `e<N>` from `engine_search(kind='system')`.
`mode`	No	`full` (default) mirrors the full definition — assessable + editable. `link_only` stores just a reference that calculates against the live engine (advanced; can't be reopened for editing).	full
`confirm`	No	Over the Aevia MCP connector this call PREVIEWS by default — it reports what would be imported and writes nothing. Read the preview, then call again with `confirm:true` to apply. Ignored in the Aevia app, where the confirmation dialog plays this role.
`workspace`	Yes	Name of the workspace to work in, as `lca_get(kind='workspaces')` lists it (backticks optional). Named on every call: several conversations can share one connection, and each names its own workspace. The connection's default is often an empty sandbox rather than the user's work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

removedInput schema / properties / engine

Removed value: -{
-  "description": "Name of the engine database, as `lca_get(kind='engines')` lists it (case-insensitive). Omitted: this connection's default engine.",
-  "maxLength": 255,
-  "minLength": 1,
-  "type": "string"
-}

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / workspace / description

Previous value: -"Name of the workspace to work in, as `lca_get(kind='workspaces')` lists it (backticks optional). Named on every call: several conversations can share one connection, and each names its own workspace."New value: +"Name of the workspace to work in, as `lca_get(kind='workspaces')` lists it (backticks optional). Named on every call: several conversations can share one connection, and each names its own workspace. The connection's default is often an empty sandbox rather than the user's work."

Changed2 schema fields changedSep 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Changed3 schema fields changedSep 24, 2026

addedInput schema / properties / engine

Added value: +{
+  "description": "Name of the engine database, as `lca_get(kind='engines')` lists it (case-insensitive). Omitted: this connection's default engine.",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / workspace

Added value: +{
+  "description": "Name of the workspace to work in, as `lca_get(kind='workspaces')` lists it (backticks optional). Named on every call: several conversations can share one connection, and each names its own workspace.",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "ref"
-]New value: +[
+  "workspace",
+  "ref"
+]

First observedSep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: server-side capture of the full definition (no graph read needed), drift tracking against the engine original, and the `mode=link_only` consequence (calculates live but cannot be reopened for editing). Idempotency is restated from the annotation and no permission/auth context is given, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and constraints are front-loaded, but the tail paragraph on restructuring steps is post-import workflow that belongs with `lca_edit_linked`/`lca_compose_linked`. It also repeats the assessable/comparable claim twice ('immediately assessable and comparable' and 'The mirror stays fully assessable/comparable').

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?

For a 4-param import with no output schema, the description covers the returned stable `s<N>`, idempotent behavior, mode tradeoffs, and the confirm preview flow. An agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the parameters are already documented, but the description adds meaning the schema lacks — why only `e<N>` is valid for `ref`, and the editability tradeoff behind `mode` (full vs link_only). The `confirm` preview flow is explained but largely mirrors the schema text.

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?

States a precise verb+resource: import an engine product system `e<N>` into a workspace as a saved `s<N>`. It distinguishes itself from siblings by spelling out the accepted ref type and by routing to `lca_run_assessment`, `lca_edit_linked`, and `lca_compose_linked` for downstream work.

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 when this is the right tool and what it rejects: only `e<N>` is accepted, a workspace `s<N>` is already imported, and a `p<N>` is not a system. It also names the concrete alternatives for restructure via `lca_edit_linked`/`lca_compose_linked`, so selection is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Aevia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?