# Asset checkout tracker - Human page: https://happytails.ai/en/business-tools/asset-checkout-tracker/ - Markdown: https://happytails.ai/en/business-tools/asset-checkout-tracker.md - Structured JSON: https://happytails.ai/agents/en/business-tools/asset-checkout-tracker/index.json - Visibility: public ## Tool capabilities | Property | Value | | --- | --- | | Tool ID | `asset-checkout-tracker` | | Category | business-tools | | Implementation | Registered implementation. Registration alone is not a production-quality guarantee. | | Browser execution | Use the visible action or interactive controls. | | Browser processing | Browser; see tool notes for network behavior. | | HTTP API | Not callable through HTTP. | | Browser-agent interface | run_current_tool | ### Implementation notes The register is replayed on this device from the events you paste, for up to 250 events. ### Inputs and settings Text input: Asset events as CSV, or a backup file. Example or placeholder shown in the interface (not a validated fixture): ```text date,tag,event,name,holder,due ``` Event is register, check-out, return, maintenance or retire. Dates use YYYY-MM-DD. Up to 400,000 characters. Review the settings before running. | Setting | Meaning | Control type | Default | Constraints | | --- | --- | --- | --- | --- | | `reference` | Reference date (empty for today) | date | "" | | | `soonDays` | Mark as due soon within (days) | number | 7 | min=0 max=366 step=1 | ### Browser-agent workflow 1. Open the human page in a browser that supports WebMCP. 2. Discover the interface exposed by that page; use its actual schema. 3. Select files on the page first when the tool requires files. 4. Call `run_current_tool` with valid input and settings. 5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links. Calls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution. ### Planning specification Up to 250 events and 100,000 characters of CSV, or a backup file of up to 500 records and 400,000 characters made by this tool. Everything is calculated on your device. Downloads: JSON report, register CSV, history CSV and a JSON backup. This describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support. ### Complete machine-readable capability record ```json { "id": "asset-checkout-tracker", "category": "business-tools", "built": true, "requirements": "Up to 250 events and 100,000 characters of CSV, or a backup file of up to 500 records and 400,000 characters made by this tool. Everything is calculated on your device. Downloads: JSON report, register CSV, history CSV and a JSON backup.", "implementation": { "fields": [ { "key": "reference", "label": "Reference date (empty for today)", "value": "", "type": "date" }, { "key": "soonDays", "label": "Mark as due soon within (days)", "value": 7, "type": "number", "min": 0, "max": 366, "step": 1 } ], "registrationFamily": "everyday-record-trackers", "inputMaxLength": 400000, "inputErrorCode": "EVERYDAY_RECORD_TRACKERS_TOO_LONG", "note": "The register is replayed on this device from the events you paste, for up to 250 events.", "experience": { "automatic": false, "single": false, "inputMaxLength": 400000, "inputMode": "text", "label": "Asset events as CSV, or a backup file", "placeholder": "date,tag,event,name,holder,due", "help": "Event is register, check-out, return, maintenance or retire. Dates use YYYY-MM-DD. Up to 400,000 characters. Review the settings before running.", "action": null }, "mode": "explicit", "interactive": false }, "execution": "Browser interface", "api": null, "browser_agent": { "supported": true, "name": "run_current_tool", "discovery": "WebMCP on the human page in a supporting browser", "verification": "See audit/API-AUDIT.md; availability is not verification" } } ``` ## Page guide Replay a log of equipment check-outs and returns to see who has each item, when it is due back and what is overdue, with a dated history. ### How to use Asset checkout tracker 1. Paste one row per event with the date, asset tag and event. 2. Register each asset first, then add check-out, return, maintenance and retire events. 3. Leave the reference date empty to use today, or enter another date. 4. Review the register and history, then download the CSV files, report or backup. How can we improve this tool? Report a problem or share an idea. Please leave out private information. Your message and the tool name go to our team via PostHog. ## Useful next steps - [Barcode generator](https://happytails.ai/en/business-tools/barcode-generator/) ([Markdown](https://happytails.ai/en/business-tools/barcode-generator.md)) - [QR code generator](https://happytails.ai/en/marketing-tools/qr-code-generator/) ([Markdown](https://happytails.ai/en/marketing-tools/qr-code-generator.md)) - [Straight line depreciation calculator](https://happytails.ai/en/business-tools/straight-line-depreciation-calculator/) ([Markdown](https://happytails.ai/en/business-tools/straight-line-depreciation-calculator.md)) ## Events and allowed steps A registered asset is available. It can be checked out, sent to maintenance or retired. A checked-out asset can be returned or sent to maintenance. Assets in maintenance come back with a return event or are retired. Other steps are refused, so the log stays consistent. ### Due dates Checked-out assets with a due date are compared with the reference date: overdue, due today, due soon within the days you choose, or later. A return clears the holder and due date. ### History The history lists every registration and status change with its date, in the order the events were entered. Events must be in date order. ### Keeping your records Nothing is uploaded. Every result includes a backup file. Paste or open that backup later to pick up where you left off, because records kept in a browser can be lost when site data is cleared.