> For the complete documentation index, see [llms.txt](https://play.equal.care/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://play.equal.care/boneyard/tools-description.md). # Tools description * Group activities: Conduct focus groups with patients to gather in-depth feedback on their care experiences, perceived benefits, and areas for improvement. * Individual Interviews: Conduct in-depth interviews with individual stakeholders to explore their personal experiences, perceived impact on quality of life, and satisfaction with the model. * Social Network Mapping and Analysis: Utilize social network analysis tools to map community relationships, engagement levels and their impacts. By employing a mix of quantitative and qualitative research methods, an evaluation can be conducted to assess the hyper-local commons-based teams model's effectiveness and identify opportunities for improvement. --- # 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://play.equal.care/boneyard/tools-description.md?ask=&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.