> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/components/menu/mc-trailing.md).

# Θ MC - Trailing

Collection: A Menu Container(MC) is a collection of the content that is possible on the right side of a menu. This allows us to keep those options that are possible on the right side of a menu organized with the ability to easily add new options.

[Styleguide Link](https://zpl.io/brGrGmO)

* Parent: [SelectList](/core/components/form/selectlist.md), [App Bar](/core/components/app-bar.md), More Icons
* Sisters: [MC - Leading](/core/components/menu/mc-leading.md), [MC - Primary](/core/components/menu/mc-primary.md)
* Child: [Label](/core/overview/label.md), [Icon](/core/overview/icon.md), [AdaptIcon](/core/overview/adapticon.md), [Avatar](/core/overview/avatar.md), [Graphic](/core/overview/graphic.md)

## Properties

* **Icon** - Primarily used to provide a second level of context to the menu option. An example of this would be a list, with its accessibility options to others (public, private).
* **Choice** - Used to give the user a visual for the menu options that are currently selected. This choice option can function as a singular choice or multi-choice.
* **Chevron** - When there's the need for hierarchical menu system we can use the chevron to indicate another level of choices in the menu structure.


---

# 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://able.bucca.com/core/components/menu/mc-trailing.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.