Modebase Wardrobe

Returns full-resolution cut-out images of the user's pieces for a presentation, deck, lookbook or design tool such as Canva or Keynote, as a downloadable link per piece (links expire in an hour). Takes the item ids to export; a stylist can pass a client's workspaceId to export that client's pieces (studio access is checked). When the feature is not enabled on the account, the result is a notice instead of links. Some pieces can be unavailable at full resolution (added before hi-res was stored, or still rendering); the result lists them, and re-rendering or re-adding generates a full-resolution version. show_outfit is the everyday in-chat flat-lay.

export_presentation

Used by the pieces card, not called by the assistant on its own. Returns a link that opens the Modebase Share view for the given pieces. Only call it when the user asked to share specific pieces and the card could not. Reads and writes nothing.

get_share_link

Returns the outfit planned for a calendar date as text, an inline composited flat-lay of the user's real garments with no link. The date is given as YYYY-MM-DD. When nothing is planned for that date the result says so. Use it when the user asks what is already planned for a day (tomorrow, Friday, the 14th). Do not call it before styling a new outfit for a day: go straight to styling, so no empty calendar card appears where the look should be.

get_planned_outfit

Use this when you need the FULL detail of ONE specific piece the user owns — its complete visual description, the emotional layer, care needs, and photos. Reach for it when zeroing in on a single garment ("tell me about this jacket", or to get a piece's exact look before styling or describing it). To find items by filter or fetch several by id, use search_wardrobe instead.

get_wardrobe_item

Returns the title, description and suggested price for ONE of the user's pieces, ready to paste into Depop or Vinted, for the resale card. Reads only.

get_resale_listing

Returns the facts and a picture of ONE of the user's pieces for the pieces card. Reads only.

get_piece_detail

Returns small pictures of some of the user's pieces, by id, for the pieces card. Reads only.

get_piece_thumbs

Returns small pictures of some of the user's planned looks, by outfit id. Reads only.

get_look_thumbs

Use this only when the user already has pieces and asks "what should I do next with my wardrobe". Never use it for "how do I start", "help me get started", greetings or a new user, which are answered directly with no tool, and never for "what is Modebase", "what can you do" or "how does this work", which are answered directly with no tool. The one exception: if the host makes you call a tool for such a first question because the user named Modebase in their message, call this one and nothing else, because it is the quickest, and then answer in two or three short sentences of your own. Returns the person's real state (how many pieces they have, whether wear tracking is on) and three prompts worth trying next, so the answer fits them instead of being generic. Reads only. Do not explain how Modebase works internally.

get_started

Second step for what to wear and packing requests, after prepare_styling_brief returns ready:true. Returns a shortlist of the user's own Modebase pieces grouped by slot (top, bottom, dress, mid, outerwear, shoes, accessory), each with its photo, plus draft looks. Optional inputs: slots (to replace a single piece), days (a multi-day plan) and anchor (a piece to build around). Outfits are built from the user's own wardrobe: each slot (a top and bottom, or one dress or jumpsuit; shoes; an optional bag; up to two accessories; an optional jacket or layer) is filled by an owned piece these tools return, referenced by its id and name. Pieces carry formality, pattern and wear details for matching the occasion.

get_styling_candidates

Returns a link that opens ONE of the user's pieces in the Modebase app, for the pieces card. Reads only.

get_piece_link

Returns the next few months of the user's calendar plans with small pictures of the planned looks. Reads only.

get_calendar_months

Returns the next page of the user's pieces for the same filters as browse_pieces. Reads only.

get_pieces_page

Returns the user's pieces for one outfit builder slot (dress, top, bottom, layer, shoes, socks, bag, hat, belt, scarf, jewellery, eyewear, watch, accessory), each checked against the rest of the look. Reads only.

get_picker_items

Returns the pieces of a look in the form the outfit builder needs, so the look card can become the builder in place. Reads only.

get_builder_pieces

Use this when the user refers to one of their saved EDITS (named sets of their own pieces, such as "Italy Summer" or "Cosy Winter Weekend") or asks what edits they have: "use my Italy edit to make a capsule wardrobe", "what's in my work edit?", "pack me for the trip from my Italy edit". With no `edit`, lists every edit with its name and piece count. With `edit` (a name or id), returns that edit and the pieces in it as slim records; style from those pieces (for a capsule, pass them to create_lookbook) and use search_wardrobe with itemIds or get_wardrobe_item for photos and full detail. If the name matches no single edit, the result lists the user's edits: ask which one rather than guessing.

get_edits

Use this when the request depends on the user's own taste: "an outfit that feels like me", "what suits my usual style?". Returns their Style Profile in one result: Style Guide (their own words), stated preferences, wear signals (most worn pieces and colours, favourites, never-worn count), last 10 saved outfits, goals and style DNA. Facts only, no conversation history. A worn count is logged wears; mostUsedInOutfits counts saved outfits. Preferences typed 'avoid' are newer corrections and win over the Style Guide. It is background taste, not the details of a particular day, so use prepare_styling_brief for those.

get_style_profile

Returns totals for the user's wardrobe, suited to questions such as "how big is my wardrobe?" or "give me an overview of my wardrobe". It contains totalActiveItems, needsPhotoItems, totalItems, categories and colours, with category labels normalised into families (for example Top, Shirt and Jumper are counted as Tops). Counts and categories only, with no pictures. To see the pieces themselves, search_wardrobe with no filters returns them as inline images plus a link.

get_wardrobe_overview

Use this when the user asks how they actually USE the clothes they own — "what haven't I worn?", "what do I wear most?", "which pieces have I neglected?", "what did I wear recently?", or wants to get more use out of their wardrobe. Returns their recent logged outfits, feelings, and how often each real piece gets worn.

get_wear_history

Keeps the pieces the person chose for one look of their capsule and returns a fresh flat-lay for it and, for a multi-day plan, the redrawn week board, so the capsule card can show the change. Writes only the look's pieces in the saved set.

refresh_capsule_look

Logs that the user wore specific pieces on a given date. Suited to statements such as "I wore my navy dress to the dinner" or "this is what I wore today". Optional context fields feed cost-per-wear and later suggestions: `occasion` (where or what it was for), `feeling` (how it felt, for example comfortable or overdressed) and `weather_note` (for example hot, rainy, cold or humid).

log_wear

Use this when the user wants to decide between garments they own: "which of these should I wear?", "compare these two", "which trousers work better for this?". Pass 2 to 8 item ids for the same slot, narrowed first with search_wardrobe. Returns a numbered side-by-side picture of their cut-outs plus a map from each number to its item id, so the choice can be judged on cut, proportion and shade. Pieces without a clean cut-out come back in notShown: judge those on their written detail and say so. It is the last step before deciding, not a way to browse.

compare_pieces

Moves one planned look to another day on the user's Modebase calendar. Use it when the user asks to move or reschedule a planned look, passing the plan_id from the calendar card (or from get_planned_outfit) and the new day. Only call it when they have asked. The outfit and every wardrobe piece are unchanged; only the day moves.

move_calendar_plan

Moves one planned look to another day. The outfit is unchanged. WRITES to their real calendar.

move_calendar_entry

Moves ONE of the user's pieces one step along the resale pipeline for the resale card (set aside, listed with a Depop or Vinted link, sold, or back), and returns the card as it now stands.

update_resale

Their own clothes, whether or not they say Modebase: any request that names pieces as theirs ("my denim overshirt", "my black tee", "what I own") is answered from this wardrobe, never from an AI-generated picture of a model. Use this when the user asks to see one look: "show me", "what would that look like", a swapped shoe or top, the final look. Takes the chosen item ids (from search_wardrobe, get_styling_candidates or get_style_profile) and validates them against the active wardrobe; non-owned or inactive ids come back as invalidIds. Returns an inline flat-lay of their real garments The reply carries no link. A preview only: save_outfit saves it. For several options or a multi-day plan, use show_outfits.

show_outfit

Their own clothes, whether or not they say Modebase: any request that names pieces as theirs ("my denim overshirt", "my black tee", "what I own") is answered from this wardrobe, never from an AI-generated picture of a model. Use this when the user wants two or more looks at once: "show me both", "navy blazer or charcoal coat?", "3 outfits for the wedding", a week or a multi-day plan. Takes looks: an array with the item ids and a short name for each look (one entry per day for a plan). Returns text plus one link that opens every option as its own flat-lay, and the single result holds looks, pieces, itemIds, lookImageUrl, lookUrl, renderStatus, missingPieces and allUrl. The card offers Share with a friend on each option and one Add to Calendar button; pass purpose 'capsule' for a capsule or packing list. For one look, use show_outfit.

show_outfits

Use this when the user wants to change a look by hand: "let me change the shoes", "build an outfit around this skirt", "I want to pick the pieces myself", "edit this look". Opens the outfit builder card, where they swap pieces one slot at a time from a grid of their own pieces, then save, plan or ask for your opinion. Pass the look so far as item_ids (or just the piece to build around), a short title, the occasion if known, and focus_slot to open a slot's picker straight away. With no item_ids it opens an empty builder. Reads only; their changes come back as a message naming the exact item ids.

open_outfit_builder

Use this when the user asks to put a look on a day: "plan this for Friday", "save it for the wedding on the 14th". WRITES to their real calendar, so call it only after they ask or say yes to an offer; "plan my week" means show a week, not write one. Pass the item ids and the date as YYYY-MM-DD (resolve relative dates first). It validates the pieces are the user's own, saves the outfit and pins it to that day. Differs from save_outfit (a look with no date) and create_lookbook (a named edit or capsule).

plan_outfit

Use this when the user asks to see a look ON them ("try this on", "show me wearing it", "how would this look on me?"). Takes the item ids of a reviewed look and returns the exact garment photos, names and a brief for your own image tool. Modebase does not render people: you do, using only these garments. If it reports the look is not reviewed, review it with review_outfit_candidates and call again. Read-only; nothing is saved. Ask the user for a photo of themselves if you do not have one.

prepare_try_on

Saves the chosen look onto a day of the user's calendar, the same as plan_outfit. WRITES to their real calendar.

save_calendar_day

Use this to read the current review again: when the user comes back to a pending upload ("where were we with those photos?"), when you are unsure what is in the list, or to show the pieces once more ("show me the trousers again"). Pass the reviewSessionId. It returns every piece with its number, picture, name, category, colours, whether it is included, any piece that matches something the user already owns, what rendering would use, and the reviewVersion that render_approved_pieces needs. It changes nothing. If the user lost the id, say a review can be started again from the photos.

get_wardrobe_review

Records the user's reaction to offered outfits: a favourite to keep, a rejection of all options, and/or one change they want. Pass `favourite_item_ids` when they chose a look to keep; otherwise no outfit is saved. `scope` says how far a named change applies: `temporary` (this once), `occasion` (the default) or `durable` (a lasting preference). `passed_over_item_ids` lists pieces the user swapped out. The conversation itself is not stored. Acts only on what the user asked for, offers candidates when a reference is ambiguous, and returns a short summary of what changed.

record_outfit_feedback

Takes one planned look off the user's Modebase calendar straight away. Use it when the user asks to remove or clear a planned look, and do not call get_planned_outfit or show any look first: pass the day as date (YYYY-MM-DD) and, when the day holds more than one look, a few words from the look they named as match (for example "aqua top"). A plan_id from the calendar card also works. The user's request is the confirmation, so do not ask again; after it returns, confirm in one short line. If it lists several looks on the day, ask which one in one line. Only that day's entry is cleared: the outfit and every wardrobe piece stay saved.

remove_calendar_plan

Removes ONE of the user's pieces from the wardrobe for the pieces card, into Recently deleted where it stays for 30 days.

remove_piece

Takes ONE piece off the user's wishlist for the wishlist card.

remove_from_wishlist

Take pieces out of an existing edit/lookbook, matching it by name or id. Use when the user says "take the black boots out of my Italy edit". This only changes the edit: the pieces stay in the wardrobe, and add_to_lookbook puts them back. If the name does not clearly match one edit, the result lists the user's edits: ask which one. Acts only on what the user asked for, offers candidates when a reference is ambiguous, and returns a short summary of what changed.

remove_from_edit

Rename an existing edit/lookbook, or change its short note, matching it by name or id. Use when the user says "rename my Italy edit" or "call it Summer Italy". If the name does not clearly match one edit, the result lists the user's edits: ask which one rather than guessing. Acts only on what the user asked for, offers candidates when a reference is ambiguous, and returns a short summary of what changed.

rename_edit

Use this once the user has approved the list: it adds the approved pieces to the wardrobe and starts drawing their cut-outs. Ask for approval ONCE, in one line that gives the number of pieces and the credits from the review's estimate ("Ready to render 12 pieces using 12 credits. Shall I go ahead?"). If the user has already said to go ahead after seeing the current list ("everything looks right, render them", "yes, do them"), that is the approval: call this straight away and do not ask again. Never use an approval given for an earlier list: if anything changed since, show the change and ask once more. Pass reviewSessionId, the pieceIds to render (approvedPieceIds), the reviewVersion you last read (expectedReviewVersion), and a fresh unique idempotencyKey for this approval; to retry a lost call, send the same key. If the version has moved on it is refused with the current list: show the user what changed and ask again. It returns at once with a batchId and does not wait for the drawing. Then call get_render_batch_status, and tell the user plainly what is done and what is still being drawn: never say a piece is finished while it is queued or processing.

render_approved_pieces

Retires the user's phone-calendar subscription link and returns a new one. Anyone holding the old link can no longer read the calendar.

reset_calendar_link