Aevia

Get workspace item

lca_get

Read-onlyIdempotent

Read a saved workspace object by ref, or list systems, results or workspaces. Takes exactly one of ref (one object's detail) or kind (a list). A ref is read in the workspace named by workspace, which it requires: each workspace numbers its objects from 1. A kind list reads that workspace, else this connection's default. Refs: s<N> → product system (live openLCA structure), a<N> → saved assessment (full impact results), c<N> → saved comparison (full matrix). An s<N> read also states the system's kind and the edit tool it takes; form='authored' returns it in the authored shape the compose and edit tools accept. Kinds: 'systems' / 'assessments' / 'comparisons' return paginated lists of this workspace, with optional filters (query, system_ref, method, assessment_status, include_stale); 'workspaces' / 'engines' list the workspaces and engine databases available, by name, marking the connection's default. Refs are short handles; UUIDs are not accepted.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	Single-entity ref. `s<N>` system, `a<N>` assessment, `c<N>` comparison. Mutually exclusive with `kind`.
`form`	No	ref='s<N>' only. 'snapshot' (default) is the structural read. 'authored' returns the system lifted back to the AUTHORED form — the shape `lca_compose_assembly` / `lca_compose_linked` speak, tagged with its `kind`, carrying a multi-stage bill of quantities' stage DAG unflattened and a linked system's `links[]` (neither of which the snapshot has). Read this before editing a system you did not just author.
`kind`	No	Collection mode. Mutually exclusive with `ref`. 'workspaces' and 'engines' are the odd ones out: they list the WORKSPACES / ENGINE DATABASES available to you rather than the contents of the current one.
`limit`	No
`query`	No	Free-text match on name/description (case-insensitive).
`method`	No	kind='assessments': substring match on method_name.
`offset`	No
`workspace`	No	Name of the workspace to read, as `lca_get(kind='workspaces')` lists it. Required with `ref`: each workspace numbers its objects from 1, so a ref is read in the workspace it came from. Omitted with `kind`: this connection's default workspace, which every conversation on the connection shares and which is often an empty sandbox.
`system_ref`	No	kind='assessments': filter to assessments on a single system.
`include_stale`	No	kind='systems': when true, also returns OUT_OF_SYNC / NOT_FOUND / UNREACHABLE / ARCHIVED rows.
`assessment_status`	No	kind='assessments': filter by status.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / workspace / description

Previous value: -"Name of the workspace to read, as `lca_get(kind='workspaces')` lists it. Omitted: this connection's default workspace, which every conversation on the connection shares and which is often an empty sandbox."New value: +"Name of the workspace to read, as `lca_get(kind='workspaces')` lists it. Required with `ref`: each workspace numbers its objects from 1, so a ref is read in the workspace it came from. Omitted with `kind`: this connection's default workspace, which every conversation on the connection shares and which is often an empty sandbox."

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / workspace / description

Previous value: -"Name of the workspace to read, as `lca_get(kind='workspaces')` lists it. Omitted: this connection's default workspace, which every conversation on the connection shares."New value: +"Name of the workspace to read, as `lca_get(kind='workspaces')` lists it. Omitted: this connection's default workspace, which every conversation on the connection shares and which is often an empty sandbox."

Changed4 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
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / system_ref / maximum
```
Added value: +9007199254740991
```

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / workspace

Added value: +{
+  "description": "Name of the workspace to read, as `lca_get(kind='workspaces')` lists it. Omitted: this connection's default workspace, which every conversation on the connection shares.",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}

First observedSep 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, yet the description adds substantial behavioral context: refs are per-workspace handles numbered from 1, UUIDs are rejected, an 's<N>' read reports the system kind and edit tool, and form='authored' returns an unflattened stage DAG and links[] the snapshot lacks.

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

Conciseness4/5

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

Purpose is front-loaded in the first clause, followed by detail, and every sentence carries real content given 11 parameters and five kinds. It is dense and unstructured (a single long paragraph that could be bulleted), but not padded.

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?

With no output schema, the description carries the return-shape burden and does so at a high level (full impact results, full matrix, paginated lists, authored vs snapshot). It does not spell out pagination fields or exact response envelopes, leaving a small gap for a complex tool.

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 82%, so the baseline is 3, but the description adds composite semantics beyond the schema: the exactly-one-of ref/kind rule, the workspace defaulting behavior for list vs ref, and the handle grammar (s<N>/a<N>/c<N>). Most individual parameter text is reinforced rather than newly added.

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 opening sentence states a specific verb and resource ('Read a saved workspace object by ref, or list systems, results or workspaces') and the tool is clearly distinguishable from sibling mutators like lca_edit_assembly, lca_compose_linked, and lca_run_assessment. The ref/kind duality is stated up front.

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

Usage Guidelines4/5

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

It explains the ref-vs-kind choice, mutual exclusivity, that ref requires a workspace, and what each kind returns, plus the key usage rule 'Read this before editing a system you did not just author.' It stops short of naming a sibling to prefer over this tool in any situation, so it is clear context rather than full when/when-not routing.

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?