> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-training-manual/design/steel-design/steel-materials.md).

# Steel Materials

How to specify yield and ultimate strengths for materials involved in steel design.

**Steel Design > Steel Materials** opens the *Steel Materials* table. (This will list *any* materials that have been defined in the model, not just steel materials.)

![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-d7b59e3d53a866d5258d2d82e2aca3f1ef30c0b9%2FSteel%20Materials.jpg?alt=media)

This table contains the materials that have been defined in **Tables > Materials**, but it lists their steel design related properties as opposed to their analysis properties. The purpose of this table is to specify values for yield strength and ultimate strength for any steel materials that are involved in a design.

{% hint style="success" %}
Tip: The materials have probably already been assigned to the members in order to get an analysis. So at this point, there is no need to Assign anything specific to members. It is only necessary to specify the material strength values for any materials that are actually involved in a steel design.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/e3d-training-manual/design/steel-design/steel-materials.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
