# Working with Containers

The *container* entity makes the *input*, *output*, or *submittedSample* container available to the scripting engine.

* The container can be queried for its name, for example:

  <pre class="language-markup" data-overflow="wrap"><code class="lang-markup">input.::container::.::name::
  </code></pre>
* Container name, UDFs / fields, and entity information can be read or written, for example:

  <pre class="language-markup" data-overflow="wrap"><code class="lang-markup">output.::container::.::example udf1:: = input.::container::.::example udf1::
  </code></pre>

Example basic expressions:

{% code overflow="wrap" %}

```markup
-exp 'output.container.::containerUDF:: = ::This is a string::'
-exp 'input.::container::.::containerUDF:: = ::This is a string::'
-exp 'submittedSample.container.::containerUDF:: = ::This is a string::'
```

{% endcode %}

{% hint style="info" %}
The word 'container' may be optionally surrounded by "::"
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.connected.illumina.com/clarity-lims/integration-toolkits/lltk/lltk-working-with-the-script/lltk-working-with-containers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.