Frondy

Add a document to sign from a file the user attached in ChatGPT, or from a link they shared (העלאת מסמך מקובץ שצורף או מקישור). Frondy downloads it itself, so the file never passes through your context. * A file attached in ChatGPT: pass it as `file`. * A link: pass it as `url` (Google Drive "anyone with the link", Dropbox, a direct download link). PDF, Word and image files are accepted; anything but a PDF is converted. In Claude, a file attached to the chat goes through begin_file_upload instead. `filename` is the name to store it under; `folder_id` is optional.

import_file

Save someone to the address book, or update a saved contact (הוספת איש קשר, עדכון איש קשר). A new contact needs a name and an email; phone and note are optional. Ask the user for a missing name or email rather than inventing one. To update, pass `contact_id` from find_contacts: only the values you pass change. ID numbers (תעודת זהות) never pass through this connector, in either direction: a Frondy contact can hold one, but only the user adds it, in the Frondy app. If asked to save or show one, say exactly that, and never put an ID number in the note or anywhere else.

save_contact

The user's current plan and how much of it they've used this period: signature requests, email/SMS/WhatsApp messages, templates, contacts, folders (חבילה, ניצול, כמה נשאר). Use it to explain why something was refused or how much is left. Describe only this plan; never list other plans, compare prices or suggest upgrading.

get_plan_usage

Look people up in the user's address book by name, email or phone, so "send it to Dana" resolves to an address (אנשי קשר, איש קשר). Returns each contact's email, phone and how many documents they've been sent. Omit `search` to list everyone.

find_contacts

Find documents and check where they stand: drafts, sent, who signed, who is still pending, expired (מסמכים, סטטוס חתימה, מי חתם, ממתין לחתימה). Lists the user's documents, optionally in one folder or with one status (draft, sent, viewed, partially_signed, signed, returned, declined, expired). Use it to find the document_id the other tools take; get_document has the details.

list_documents

Find the user's saved templates: documents with their fields already placed, ready to reuse (תבניות, תבנית). Optionally filter by a word in the name or description, or by category. Start a document from one with create_document_from_template.

list_templates

Organize documents into folders (תיקיות): list folders, create one, move a document into a folder, or move a folder under another folder. "list" `parent_id` → that folder's children; omit → top level. "create" A folder called `name` under `parent_id` (omit → top level). "move_document" Move `document_id` into `folder_id` (omit → out of any folder). "move_folder" Move `folder_id` under `parent_id` (omit → top level). When the user names a folder ("the Cohen folder"), find its id with "list". Duplicate names at one level, and moving a folder into itself, are refused.

manage_folders

Everything about one document: its status, each signer and whether they signed, and the fields placed on it; optionally its history (sent, viewed, signed) and download links for the original and the signed PDF (פרטי מסמך, היסטוריה, הורדת המסמך החתום). Download links are time-limited: give them to the user right away.

get_document

Mark where people sign: add signature boxes and other fields (date, name, phone, email, text, ID number, stamp/חותמת) to a document before sending it (שדות חתימה, איפה לחתום). Coordinates are fractions of the page (0 to 1) from its top-left corner. Look at the page with `get_document_page_image` first and place by eye. Most Frondy documents are Hebrew/RTL: signature lines usually sit near the BOTTOM on the RIGHT, often on a line labeled 'חתימה' or 'חתימת הלקוח'. Set `allow_seal_upload` on a signature field when the user mentions a stamp (חותמת). A `national_id` field is filled in by the signer: never give it a default_value, and never ask the user for an ID number. Safe to retry: a field identical to one already on the document is reported under `already_present_field_ids` instead of being added twice. To fix a misplaced field, remove it with `remove_signature_fields` and add it again.

add_signature_fields

Step 1 of sending a document for signature — by email, SMS, WhatsApp or a signing link (שליחה לחתימה, לשלוח לחתימה). Checks the request and returns a summary to show the user. Nothing is sent. recipients: each needs a way to be reached — an email for email, a phone for SMS or WhatsApp. Several recipients each get their own link and sign in parallel: there is no signing order. 2+ recipients needs a paid plan. send_email: email each recipient their link (default). send_sms: also text the link (uses the plan's SMS allowance and a verified sender). With send_email false this is an SMS-only send: a phone alone is enough, don't ask for an email. send_whatsapp: the USER pastes the link into WhatsApp; Frondy sends nothing. One recipient only. All channels false: nothing is delivered; the user gets the links to pass on. email_subject / email_body: optional plain text, with placeholders {{filename}}, {{signing_url}}, {{recipient_name}}, {{sender_name}}. Omit to use the account's default invitation. Show the user the summary — the document, who gets it and how, the message and any warnings — and call send_for_signature with `preview_id` only after they confirm in this conversation. A preview is valid for 15 minutes.

preview_signature_request