> For the complete documentation index, see [llms.txt](https://docs.metapool.app/master/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metapool.app/master/tokenomics-and-governance/mpdao-governance/why-mpdao.md).
# Why mpDAO?
mpDAO serves a crucial purpose by addressing coordination and decentralization challenges that arise among the various stakeholders involved with Meta Pool. It provides clarity on how the protocol will be implemented and managed, fostering transparency and a more inclusive decision-making process.
This approach empowers the community to actively participate in the protocol's evolution, ensuring that Meta Pool remains a dynamic and responsive platform that meets the needs and aspirations of its users worldwide.
$META Token holders are the driving force behind mpDAO, shaping its development and governance. Their ownership empowers them to influence resource allocation, proposal approval, and Meta Pool's strategic direction. Through participation in discussions, voting, and feedback, they contribute to a democratic decision-making process that aligns the mpDAO with the community's vision.
---
# 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.metapool.app/master/tokenomics-and-governance/mpdao-governance/why-mpdao.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.