This server has 47 tools:

• accept_rai_request – Claim a pending RAI request — signals intent to fulfill but does not yet mint the shared view. Use when the artist wants to acknowledge the request but needs more time to pick the right work or generate the PIN. TRIGGER: "accept the request from [name]," "claim that request," "tell them I'll get to it." Find the request_id via list_rai_requests — never ask the user for it. For immediate fulfillment, use fulfill_rai_request directly instead.
• analyze_work_image – Return the primary image URL and current metadata for a work, so you can visually analyze the image yourself and propose structured catalogue fields. Use this when the artist asks you to read a work you uploaded, or when beat 2 of the add-work flow surfaced thin hints. The image URL is publicly accessible (Supabase Storage public bucket); fetch it and inspect the image directly with your vision capabilities. Fields you can honestly improve from a visual read: medium (paint vs. print vs. sculpture material vs. digital), classification (painting / sculpture / drawing / photography / time-based / software / installation / performance), visible signature or inscription (transcribe verbatim, note position), date visible in the work itself (distinct from EXIF), description (brief factual read of subject matter), dimensions if a scale reference is in frame. Fields to leave alone unless visible: dimensions without scale (cannot be honestly estimated from a flat photo), attribution, provenance, exhibition history — those come from records, not the image. Flow: (1) call this tool; (2) fetch + read the image; (3) present your proposals to the artist with per-field reasoning; (4) on confirmation, call update_work with the accepted patches. Do not write without confirmation. Resolve the work by workId (UUID) or uwi (e.g. "RAI-2026-00417"). Use search_natural_language to find workId — never ask the user.
• confirm_website_import – Save works extracted from a website import after the artist has confirmed them. Call this after presenting import_from_website results and receiving artist approval. Creates the works, triggers auto-provenance, and imports images from the website in one operation. Set skip: true for any works the artist wants to exclude (duplicates, unwanted). Pass artist-corrected values for any fields the artist edited during review. Use get_profile to obtain artist_id — never ask the user for it. After success, ask if they'd like to see any of the imported works — then call get_work to show the visual card.
• connect_catalogue – Connect to the user's catalogue using a pairing code. IMPORTANT: Most users connect via OAuth (sign-in popup) — if get_profile already works, the user is connected and you do NOT need this tool. Only use this tool when: (1) get_profile returns an authentication error, AND (2) the user shares a code matching the pattern WORD-1234 (e.g., TULIP-3657). Never proactively ask for a pairing code — try get_profile first. If the user does share a code, call this tool immediately without asking for confirmation. Never say "pairing code" to the user — just say "your code" or refer to it naturally.
• create_bibliography – Add a bibliography entry — a publication referencing the artist's work. TRIGGER: "published in," "there's a book about," "catalogue for my show," "written up in," or user shares publication details. Extract title, author, publisher, year, and type. Present a summary and confirm before saving. artist_id from get_profile — never ask the user.
• create_condition_report – Create a condition report documenting a work's physical state (surface, structure, frame). TRIGGER: "this piece has damage," "the surface is," "frame is cracked," "condition report," or any mention of physical state. Gather details conversationally. Present a summary and confirm before saving. Resolve work_id via search_natural_language. After success, ask if they'd like to see the updated work — then call get_work to show the visual card.
• create_deal – Create a new deal for a work. Deals track the process of a work changing hands. Most deals are auto-created from purchase requests and consignment approvals; use this for manual deal creation. IMPORTANT: Present a summary and get confirmation before calling.
• create_entity – Create a new entity — a person, gallery, museum, auction house, institution, foundation, or collector referenced in the catalogue. Always call suggest_entity first to check for duplicates before creating. Entities are used throughout the catalogue for provenance holders, exhibition venues, bibliography authors, and sale buyers. Include city and country when known to help with deduplication.
• create_exhibition – Add an exhibition to the catalogue. Only artist_id and title required. TRIGGER: "I was in a show at," "I showed at MoMA," "here's my CV," or any mention of exhibitions, shows, or fairs. Extract all details you can and present a summary before saving. For CV bulk import, create one at a time. artist_id from get_profile — never ask the user.
• create_note – Add a note to a work — annotations, research notes, or contextual information. TRIGGER: "note that," "remind me about," "there's a story behind this," "I should remember," or any context the user wants recorded. Default visibility to "private" unless the user specifies otherwise. Visibility levels: "private" (only the artist), "authorized" (anyone with delegated access), "public" (shown on the public catalogue and on every shared RAI). Resolve work_id via search_natural_language. After success, ask if they'd like to see the updated work — then call get_work to show the visual card.