> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/team-administration/hosting-competitions/tournament-manager/tools.md). # Tools #### Team Checkin Team Checkin is used when teams arrive at an event to mark them as present. A volunteer should check in a team and give them any information needed for the event as well as checking that all paperwork that is needed has been received. #### Inspection Inspection is used when checking a team's robot for legality. This tool does not show all criteria for a team to pass inspection, which is found [here](https://www.roboticseducation.org/resources_library/vrc-robot-inspection-checklist/). A team must pass inspection to be added to the schedule. On Pit displays, teams that are checked in show up as grey, teams that are partially inspected are shown as yellow, and teams that have passed inspection are shown as green. #### Announcements Announcements are used to show text at the bottom of pit displays. Once published they are shown until the end time that is set when the message is published. Multiple messages can be shown at the same time. #### Mobile Devices Mobile Devices is a terminal to setup devices on the same network that are running the [TMMobile](https://www.roboticseducation.org/app/tm-mobile/) app. More information can be found here with a full tutorial on how to pair different devices. --- # 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://wiki.purduesigbots.com/team-administration/hosting-competitions/tournament-manager/tools.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.