Stowra

View saved version →

---
name: stowra-gear-inventory
description: Inspect and organize a user's Stowra gear inventory, including item details, weights, stock, tags, updates, trash, and restore. Use for requests about gear the user owns or tracks; do not use for general shopping advice or trip planning alone.
---

# Stowra Gear Inventory

Use Stowra as the source of truth. Never invent record IDs, weights, prices, tag IDs, or inventory facts.

## Resolve the target

- Start with `list_gear_items` when identifying an item, checking for duplicates, or reviewing inventory.
- Use `get_gear_item` when full details, photos, tags, or sports are needed.
- If several records plausibly match, show the candidates and ask the user which one they mean before writing.

## Create or update gear

- Before `create_gear_items`, search for likely duplicates. Create only the items the user actually requested.
- Weights use milligrams. Do not estimate a missing weight. Use `weightSource: "measured"` only for a user-measured value and `"manufacturer"` for a documented specification.
- `update_gear_items` applies the same supplied fields to every selected ID. A name can be changed only when exactly one ID is supplied.
- A weight update must include both `weightMg` and `weightSource`; never infer the provenance of an existing weight.
- Preserve omitted fields. Do not fill optional brand, model, category, price, stock quantity, or notes from assumptions.

## Manage tags and removal

- Use `add_gear_item_tags` to attach an existing tag and `remove_gear_item_tags` to detach one.
- Both tools require an existing `tagId`. The current MCP surface cannot list or create tags. If no trustworthy tag ID is available from prior results or the conversation, explain that limitation instead of inventing one.
- `delete_gear_items` moves gear to trash; it does not delete kit or loadout lines. `restore_gear_items` requires an ID retained from the delete result or earlier context because trashed gear is hidden from listing.
- Never broaden a destructive request beyond the item IDs the user identified.

## Report the outcome

Summarize what was read or changed, call out failures or ambiguous matches, and include the returned batch ID for writes. If the user asks to reverse a change, call `undo_batch` with that exact batch ID; never guess or substitute the most recent batch.

Referenced files: 1

View saved version →

---
name: stowra-kit-builder
description: Build and maintain reusable Stowra gear kits, or copy a kit into a trip loadout. Use when the user wants a reusable bundle such as a sleep system, first-aid kit, or activity setup; do not use for a one-off packing list with no kit workflow.
---

# Stowra Kit Builder

A kit is a reusable bundle, not a trip. Use Stowra records as the source of truth and never invent kit, gear, line, loadout, or section IDs.

## Resolve the kit and gear

- Use `list_kits` to find candidate kits and `get_kit` to inspect a kit's current lines before changing it.
- Use `list_gear_items` to resolve the gear the user names. If a required item does not exist, ask whether to create it with `create_gear_items`; do not silently create substitutes.
- If several kits or gear items match, ask the user to choose before writing.

## Build and maintain kits

- `create_kits` creates empty reusable bundles. Add existing gear with `add_kit_items` only after resolving each gear item ID.
- Use `update_kits` to rename a kit or change its description while preserving fields the user did not mention.
- Quantities and classifications belong to kit lines. Use `get_kit` before `update_kit_items` or `remove_kit_items`, because those tools require kit-line IDs rather than gear-item IDs.
- `remove_kit_items` permanently removes the selected lines unless its returned batch is undone; it does not remove the underlying gear.
- `delete_kits` moves the bundle to trash while leaving gear untouched. `restore_kits` requires an ID retained from the delete result or earlier context because trashed kits are hidden from listing.
- Never broaden an update or removal beyond the lines or kits the user identified.

## Copy a kit into a trip

- Resolve the source with `get_kit` and the destination with `list_loadouts` or `get_loadout` before calling `add_kit_to_loadout`.
- Supply a section ID only when the destination section has been resolved from `get_loadout`.
- Copying creates loadout lines that remember their source kit; later kit changes do not alter an already packed trip.
- Report any skipped kit lines. Trashed gear is skipped rather than copied, and an empty or fully skipped kit cannot be added.

## Report the outcome

Summarize the resulting kit or copied loadout lines, distinguish line IDs from gear IDs, and include the returned batch ID. If the user asks to reverse a change, call `undo_batch` with that exact batch ID; never guess a batch.

Referenced files: 1

View saved version →

---
name: stowra-trip-loadouts
description: Plan and manage Stowra trip loadouts, including packing-list gear, sections, participants, readiness, packing status, and weight summaries. Use for a specific trip or packing list; do not use for general travel, route, or weather advice.
---

# Stowra Trip Loadouts

A loadout is a trip-specific packing list. Use Stowra as the source of truth and never invent loadout, section, profile, gear, or line IDs.

## Resolve the trip and related records

- Use `list_loadouts` to find the trip and `get_loadout` to inspect its sections, participants, and lines before changing it.
- Resolve named gear with `list_gear_items` and named people with `list_profiles`. Profiles represent people in the workspace, not login accounts.
- Ask the user to choose when several loadouts, gear items, sections, or profiles plausibly match.

## Build the packing list

- Use `create_loadouts` for new trips, preserving omitted dates or descriptions instead of inventing them.
- Use `update_loadouts` for an existing trip's name, description, dates, or status while preserving omitted fields.
- Add individual gear with `add_loadout_items`. When the user wants a whole reusable kit, resolve it with `list_kits` and `get_kit`, then use `add_kit_to_loadout`.
- Add organization with `add_loadout_sections`. Set `containerGearItemId` only to a resolved gear item that represents the physical container.
- Add people with `add_loadout_participants`, then use `update_loadout_participants` only for readiness changes.

## Update or remove trip data

- `update_loadout_items` and `remove_loadout_items` require loadout-line IDs from `get_loadout`, not gear-item IDs.
- Updating several loadout lines applies the same supplied values to each one. Preserve omitted fields.
- Use `update_loadout_sections` for section labels, order, or containers. `remove_loadout_sections` keeps the section's lines but leaves them outside any section.
- Use `remove_loadout_participants` only for the resolved profiles. Their profiles remain in the workspace, and existing line assignments are preserved.
- Removing a loadout line does not remove the underlying gear.
- `delete_loadouts` moves trips to trash and leaves inventory gear intact. `restore_loadouts` requires an ID retained from the delete result or earlier context.
- Never broaden a destructive request beyond the exact trips, lines, sections, or participants the user identified.

## Explain weight and readiness

- Use `list_loadout_weights` for total and base weights. Values are in milligrams; convert units for presentation only when useful and retain exact values when precision matters.
- Base weight excludes worn and consumable items. `unknownCount` means the totals are understated; do not treat unknown weights as confirmed zeroes.
- After multi-step changes, use `get_loadout` when the user needs the final organized packing list.

## Report the outcome

Summarize the trip state, changed records, skipped or failed operations, packing/readiness status, and any weight caveats. Include the returned batch ID for writes. If the user asks to reverse a change, call `undo_batch` with that exact batch ID; never guess a batch.

Referenced files: 1