> 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/match-control/inputting-scores-on-tm-mobile.md).
# Inputting Scores on TM Mobile
TM Mobile Scoring
Start by selecting a match to score on the left screen, and the middle screen will open. This is similar to the desktop version but can be used for live scoring. The bottom 3 buttons are used to delete the score, refresh the score (if 2+ devices are being used) and to save the score.
{% hint style="info" %}
If 2 mobile devices are used to score the same match, the last device to save the score is the published one. Either confirm they are identical or only save on one.
{% endhint %}
Skills matches are scored similarly to the desktop version as well, with a team selection similar to the left screen, and runs saved with scores on the right screen. Teams normally run roughly 3 of each type of skills run however TM will not limit the total number, only notify that the team has run the allotted number.
---
# 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/match-control/inputting-scores-on-tm-mobile.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.
