> For the complete documentation index, see [llms.txt](https://docs.sacra.cc/sacra-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sacra.cc/sacra-whitepaper/game-overview/inventory/items-overview/slot-structure.md).
# Slot Structure
In the All Inventory section, users can access detailed information about each item slot, which typically includes:
1. **ID:** This is a unique identifier for each item slot, making it easier for users to manage and differentiate their inventory.
2. **Augmentation Level:** The augmentation level of an item slot indicates how many times the item has been enhanced or upgraded.
3. **Magic Attack:** Magic attack is a characteristic of certain item slots, denoting their capacity for dealing magical damage.
4. **Durability:** When an item's durability approaches zero, the item slot will display a "broken" status, highlighted in red
. This visual indicator serves as a warning to players, making it clear that the item is at risk of breaking soon. If one of your equipped item will be broken soon, you will be notified via an icon 
in the menu or next to your hero.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sacra.cc/sacra-whitepaper/game-overview/inventory/items-overview/slot-structure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.