{"serverId":"mcp-registry/com.simafri/professional-email","tools":[{"name":"add_mailbox_alias","fixed":{"name":"add_mailbox_alias","description":"Points another address at a mailbox: mail sent to it lands in that box, threads there and counts against the storage of the account. An alias has no password, no seat and no storage of its own, and the number one box may carry is limited; list_mailboxes gives the limit and what is already used.","inputSchema":{"type":"object","required":["address","alias"],"properties":{"alias":{"type":"string","description":"The other address to point at this box, for example \"webmaster@sonentreprise.com\". It must be free and on a domain of the account: an address already used by the platform, or one on the domain of another account, is refused."},"address":{"type":"string","description":"The address of the mailbox, for example \"marie@sonentreprise.com\": call list_mailboxes to find it. A support queue is not a mailbox: it has no holder and takes no alias."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Add another name to a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":251,"tokensAfter":251},{"name":"add_mailbox_holder","fixed":{"name":"add_mailbox_holder","description":"Puts a person of the account on a mailbox, which is what lets them read it. This is how a company takes back the correspondence of someone who has left; it is recorded, and the box shows it to whoever is on it. A box may be held by several people.","inputSchema":{"type":"object","required":["address","person"],"properties":{"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."},"address":{"type":"string","description":"The address of the mailbox, for example \"marie@sonentreprise.com\": call list_mailboxes to find it. A support queue is not a mailbox: it has no holder and takes no alias."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Put someone on a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":210,"tokensAfter":210},{"name":"add_note","fixed":{"name":"add_note","description":"Leaves a note on a thread for the people who work it: shown on the thread screen beside the messages, marked as internal, and in \"notes\" of get_conversation. It never reaches the correspondent: it is not sent, not quoted in a reply and not part of the mail. It is where the context goes when you hand a thread to a colleague, what you found, what was agreed, why you stopped. It does not change the status of the thread nor its place in the list. It is signed with the name of the person this connect","inputSchema":{"type":"object","required":["conversation_id","body"],"properties":{"body":{"type":"string","description":"The text of the note, plain text, up to 10000 characters."},"attachments":{"type":"array","items":{"type":"object","properties":{"filename":{"type":"string","description":"The name the recipient sees, extension included. Inline form only."},"upload_id":{"type":"string","description":"A file already sent to its upload address, as create_attachment_upload gives it. The other fields are then left out: the name and the media type are the ones the slot was opened with."},"content_type":{"type":"string","description":"The media type, for example \"application/pdf\". Derived from the name when left out."},"content_base64":{"type":"string","description":"The file itself, base64 encoded. Inline form only, and only worth it for something small."}}},"description":"Files for the team, joined to the note, up to 10 and 7 MiB in total. Each one is named EITHER by \"upload_id\", a file already pushed to a slot from create_attachment_upload, OR inline by \"filename\" and \"content_base64\". They are never sent to anyone."},"conversation_id":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"maxItems":50,"minItems":1}],"description":"The id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Leave an internal note on a thread"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":544,"tokensAfter":544},{"name":"add_queue_operator","fixed":{"name":"add_queue_operator","description":"Names a person of the account on a helpdesk queue, which is what lets them work it: they see the threads that arrived on that address, and none of the others. This is how a shared queue is split between colleagues, one department to each. Somebody whose rank already opens every queue is refused rather than given a grant that changes nothing.","inputSchema":{"type":"object","required":["person","queue"],"properties":{"queue":{"type":"string","description":"The address of the helpdesk queue, for example \"contact@sonentreprise.com\": call list_sender_addresses to find it. A mailbox is not a queue: it is one person's correspondence and it is handed over with add_mailbox_holder."},"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Put someone on a helpdesk queue"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":250,"tokensAfter":250},{"name":"add_team_member","fixed":{"name":"add_team_member","description":"Puts a person of the account in a team, whatever their rank. It opens no queue: they see the threads handed to the team only on the queues they already work, which add_queue_operator decides. A deactivated account is refused.","inputSchema":{"type":"object","required":["team","person"],"properties":{"team":{"type":"string","description":"The slug of the team, as list_teams gives it."},"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Put someone in a team"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":166,"tokensAfter":166},{"name":"approve_draft","fixed":{"name":"approve_draft","description":"Sends a draft to the contact, with the text as given in \"body\" when you edited it. The draft keeps the original wording and the sent message keeps what actually left, so the two stay comparable afterwards.","inputSchema":{"type":"object","required":["draft_id"],"properties":{"body":{"type":"string","description":"The text to send instead of the one Iris wrote. Left out, the draft goes out as it stands."},"status":{"enum":["answered","in_progress","closed"],"type":"string","description":"Where the thread stands once the answer is out. Left out, \"answered\". \"in_progress\" for an answer that only holds the contact while someone keeps working on the case (an acknowledgement, a request passed on), \"closed\" for the answer that settles it."},"draft_id":{"type":"string","description":"The id of the draft, as list_drafts gives it."},"attachments":{"type":"array","items":{"type":"object","properties":{"filename":{"type":"string","description":"The name the recipient sees, extension included. Inline form only."},"upload_id":{"type":"string","description":"A file already sent to its upload address, as create_attachment_upload gives it. The other fields are then left out: the name and the media type are the ones the slot was opened with."},"content_type":{"type":"string","description":"The media type, for example \"application/pdf\". Derived from the name when left out."},"content_base64":{"type":"string","description":"The file itself, base64 encoded. Inline form only, and only worth it for something small."}}},"description":"Files to send along, up to 10 and 7 MiB in total. Each one is named EITHER by \"upload_id\", a file already pushed to a slot from create_attachment_upload, OR inline by \"filename\" and \"content_base64\". Prefer the upload for anything but a few lines of text: a file written out as base64 has to be produced character by character, which a real document overruns long before the 7 MiB cap."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Approve a draft and send it"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":551,"tokensAfter":551},{"name":"assign_conversation","fixed":{"name":"assign_conversation","description":"Puts a colleague's name on a thread of a helpdesk queue: what says, to everyone working that queue, that this one is being dealt with and by whom. It hands over the WORK and not the access, so the thread stays readable by the whole team and nobody loses sight of it. Somebody who does not work that queue is refused rather than named on a thread they cannot open, and so is a deactivated account: put them on the queue first with add_queue_operator. Threads of a mailbox are refused too, a box being ","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"team":{"type":"string","description":"The slug of a team of the account, as list_teams gives it, in place of \"person\"."},"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."},"conversation_id":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"maxItems":50,"minItems":1}],"description":"The id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Say who is handling a thread"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":330,"tokensAfter":330},{"name":"cancel_scheduled_send","fixed":{"name":"cancel_scheduled_send","description":"Calls a scheduled message back before it leaves. Nothing is sent and nothing is lost: it becomes an unsent draft again, with its recipients, text and files, whose draft_id the answer gives (delete_compose_draft throws it away). Refused once the message is already leaving.","inputSchema":{"type":"object","required":["scheduled_send_id"],"properties":{"scheduled_send_id":{"type":"string","description":"The id of the scheduled message, as send_email, reply_to_conversation or list_scheduled_sends gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Cancel a scheduled message"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":156,"tokensAfter":156},{"name":"create_attachment_upload","fixed":{"name":"create_attachment_upload","description":"Opens an address to send a file to, so that a message can attach it without carrying it. Answers with an upload_id and an upload_url: PUT the bytes to that address in one request (no key, nothing to sign, for example `curl -T report.pdf \"<upload_url>\"`), then pass {\"upload_id\": \"...\"} in the \"attachments\" of send_email, reply_to_conversation, forward_conversation or approve_draft. This is the way to attach a real document: the inline base64 form asks you to write the whole file out yourself, whi","inputSchema":{"type":"object","required":["filename"],"properties":{"filename":{"type":"string","description":"The name the recipient will see, extension included. It is fixed here: the message that attaches the file does not rename it."},"content_type":{"type":"string","description":"The media type, for example \"application/pdf\". Left out, it is read from the bytes when they arrive."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Open an upload for a file to send"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":265,"tokensAfter":265},{"name":"create_contact","fixed":{"name":"create_contact","description":"Opens a fiche for someone before any exchange has happened. An address the account already holds returns that contact as it stands, so calling it twice keeps one fiche.","inputSchema":{"type":"object","required":["email"],"properties":{"name":{"type":"string","description":"The name of the person."},"email":{"type":"string","description":"Their email address, which identifies the fiche."},"phone":{"type":"string","description":"Their phone number, as they gave it."},"sector":{"type":"string","description":"The sector they work in."},"address":{"type":"string","description":"Their postal address."},"language":{"type":"string","description":"The language to write to them in, as a code such as \"fr\", \"en\" or \"mg\"."},"company_name":{"type":"string","description":"The company they write for."},"project_type":{"type":"string","description":"What they came for."},"contact_title":{"type":"string","description":"Their role there, for example \"Directrice generale\"."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Open a contact fiche"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":284,"tokensAfter":284},{"name":"create_folder","fixed":{"name":"create_folder","description":"Makes a folder in a mailbox, at the top or under another folder, to file threads in. Every holder of the box sees it, in the webmail and in their mail client. A name holds no \"/\", \"*\" nor \"%\", is unique among its neighbours, and at the top is none of the six every mailbox has.","inputSchema":{"type":"object","required":["box","name"],"properties":{"box":{"type":"string","description":"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders."},"name":{"type":"string","description":"The name of the folder, 200 characters at most."},"parent_id":{"type":"string","description":"The folder it goes under, by its id from list_folders. Left out, it goes at the top."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Make a folder in a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":243,"tokensAfter":243},{"name":"create_knowledge","fixed":{"name":"create_knowledge","description":"Adds a doc to the playbook Iris reads, scoped to the brands and addresses you give it. Use it to record a price list, an argument that works or a rule to follow, once, where every future draft will find it.","inputSchema":{"type":"object","required":["title","content"],"properties":{"title":{"type":"string","description":"The title of the doc, unique in the account."},"brands":{"type":"array","items":{"type":"string"},"description":"The brand slugs this doc applies to, from list_brands. An empty list applies it to the whole account."},"content":{"type":"string","description":"The doc itself, in Markdown. This is the text Iris reads before drafting."},"addresses":{"type":"array","items":{"type":"string"},"description":"The inbound addresses this doc applies to, from list_sender_addresses. An empty list applies it to every address of the brands above."},"sort_order":{"type":"integer","description":"Where the doc sits in the reading order, lowest first."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Add a knowledge doc"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":281,"tokensAfter":281},{"name":"create_team","fixed":{"name":"create_team","description":"Opens a team by its name; its slug comes from the name and never changes, even when the team is renamed. A name too close to one the account already has is refused. Put people in it with add_team_member.","inputSchema":{"type":"object","required":["name"],"properties":{"name":{"type":"string","description":"The name the team is shown under, 1 to 80 characters."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Create a team"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":113,"tokensAfter":113},{"name":"delete_compose_draft","fixed":{"name":"delete_compose_draft","description":"Throws away a message that was started and will not be sent. Nothing was ever delivered, so nothing is lost but the text itself.","inputSchema":{"type":"object","required":["draft_id"],"properties":{"draft_id":{"type":"string","description":"The id of the unsent message, as list_compose_drafts gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Discard a message never sent"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":99,"tokensAfter":99},{"name":"delete_conversation","fixed":{"name":"delete_conversation","description":"Deletes a thread and everything it holds: every message, the drafts written on it, and the files that came with them, down to the bytes they were stored as. This is FINAL and there is no trash to fish it back out of, so it is not the gesture for tidying an inbox: file_conversation with \"trash\" is, and it keeps the thread readable and restorable. Use this only when the record itself must not remain, and when the person asking knows that is what they are asking for. The contact fiche stays, and so","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Delete a conversation for good"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":206,"tokensAfter":206},{"name":"delete_folder","fixed":{"name":"delete_folder","description":"Deletes a folder a person made and the folders under it. Their threads go to the Trash, where they stay readable and restorable for 30 days by default, or for the retention set on the account; nothing is deleted for good. The answer says how many went there.","inputSchema":{"type":"object","required":["folder_id"],"properties":{"folder_id":{"type":"string","description":"The folder, by its id from list_folders."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Delete a folder"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":128,"tokensAfter":128},{"name":"delete_knowledge","fixed":{"name":"delete_knowledge","description":"Takes a doc out of the playbook, with every version it ever had. This is FINAL and there is no trash: Iris stops reading it from the next draft on. A doc that is merely out of date is better rewritten with update_knowledge, which keeps the previous version dated in its history.","inputSchema":{"type":"object","required":["doc_id"],"properties":{"doc_id":{"type":"string","description":"The id of the doc, as list_knowledge gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Remove a knowledge doc"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":134,"tokensAfter":134},{"name":"delete_note","fixed":{"name":"delete_note","description":"Deletes an internal note from a thread, and the files it carried with it: a note left on the wrong thread, or one that is no longer true. It cannot be undone; to fix a word, update_note keeps the note. Allowed to the author of the note and to a manager or the owner of the account; anyone else is refused. One note at a time.","inputSchema":{"type":"object","required":["conversation_id","note_id"],"properties":{"note_id":{"type":"string","description":"The id of the note, as \"notes\" of get_conversation gives it."},"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Delete an internal note"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":187,"tokensAfter":187},{"name":"delete_team","fixed":{"name":"delete_team","description":"Deletes a team. The threads handed to it go back to their queue with nobody's name on them; the threads one of its members took stay on that member's name.","inputSchema":{"type":"object","required":["team"],"properties":{"team":{"type":"string","description":"The slug of the team, as list_teams gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Delete a team"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":97,"tokensAfter":97},{"name":"get_attachment","fixed":{"name":"get_attachment","description":"Reads a file attached to a message and gives back its CONTENT. Text comes back as text, whatever the sender labelled it: a CSV, an XML, a JSON, a Markdown or a log read as text even when they arrive as application/octet-stream. An image comes back as the image itself, a PDF comes back as the text it holds, which is how an invoice, a quote or a contract is read, and a .gz or a .zip is opened to give the text it holds, which is how a DMARC report is read. An office document comes back as its text,","inputSchema":{"type":"object","required":["conversation_id","attachment_id"],"properties":{"attachment_id":{"type":"string","description":"The id of the attachment, as get_conversation gives it on the message that carries it."},"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":true},"title":"Read an attachment"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":246,"tokensAfter":246},{"name":"get_contact","fixed":{"name":"get_contact","description":"Reads one contact whole: their fiche, the addresses they write from and where each field came from.","inputSchema":{"type":"object","required":["contact_id"],"properties":{"contact_id":{"type":"string","description":"The id of the contact, as list_contacts gives it."}}},"annotations":{"readOnlyHint":true},"title":"Read a contact fiche"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":86,"tokensAfter":86},{"name":"get_conversation","fixed":{"name":"get_conversation","description":"Reads one thread whole: every message in order with its direction, its language and its attachments, the contact fiche, the mailbox the thread arrived through, the draft awaiting review when there is one, and in \"notes\" what the team left on the thread for each other, oldest first, with who wrote each one. Notes are never part of \"messages\" and were never sent to anyone. A message the mailbox sent carries \"delivery\" when the mail system tracked it: per recipient (Bcc included), \"state\" is \"deliv","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"conversation_id":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"maxItems":20,"minItems":1}],"description":"The id of the conversation, as list_conversations gives it, or a list of up to 20 ids to do the same to every one of them in a single call."}}},"annotations":{"readOnlyHint":true},"title":"Read a conversation"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":252,"tokensAfter":252},{"name":"get_customer_card","fixed":{"name":"get_customer_card","description":"Reads the customer card of a helpdesk ticket: what the account's own system (its client area, CRM or ERP) knows about the correspondent, asked live by their address, such as their account, their services and when they renew, and what they owe. \"status\" says \"found\" with the card, \"not_found\" when that system does not know them, \"unavailable\" when it did not answer (ask again later, it says nothing about the customer), \"unverified\" when it was not asked because the latest message names its corres","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":true},"title":"Read what the account knows about a ticket's customer"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":207,"tokensAfter":207},{"name":"get_settings","fixed":{"name":"get_settings","description":"Reads the settings of the account, starting with whether an incoming message has Iris draft an answer on its own. \"own_domain_spoofs\" says what the account does with a mail that shows one of its own domains and fails DMARC: \"filed\" when such a mail goes to Spam (to the Trash, closed, on a helpdesk queue) as it arrives, and \"exempt_senders\" for the addresses of the account that keep arriving normally although they fail. It is read here, and the support team changes it on request.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"Read the account settings"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":165,"tokensAfter":165},{"name":"invite_person","fixed":{"name":"invite_person","description":"Opens an access for a colleague without a password: an invitation goes to send_to, and whoever opens it chooses the password from its link, which opens for seven days and once. The link is never shown here, you included, and the record names where it went. send_to is the person themselves at an address they already read, or the box of whoever sets up the team's access. A mailbox of this platform is accepted only when an active person already signs in to it; one nobody can open yet, such as the n","inputSchema":{"type":"object","required":["email","send_to"],"properties":{"name":{"type":"string","description":"Their name, as the team will read it. Required for somebody new."},"role":{"enum":["operator","manager"],"type":"string","description":"Operator by default: they see the queues and boxes they are given. A manager sees every queue and runs the settings."},"email":{"type":"string","description":"The address the person will sign in with, for example their new mailbox \"zoe@sonentreprise.com\"."},"locale":{"enum":["fr","en"],"type":"string","description":"The language of the invitation and of their screens."},"send_to":{"type":"string","description":"Where the invitation goes: an address the person already reads, or the box of whoever sets up the team's access, for example \"it@sonentreprise.com\". A box of this platform nobody signs in to yet is refused."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Invite someone to the account"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":395,"tokensAfter":395},{"name":"list_blocked_senders","fixed":{"name":"list_blocked_senders","description":"Lists the addresses whose mail this account files straight into Spam, most recently blocked first, with the day each was blocked. A block is what report_spam leaves behind, so this is where a rule the account is living under becomes visible again: a sender blocked from a thread long since deleted appears here and nowhere else.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the blocked senders"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":122,"tokensAfter":122},{"name":"list_brands","fixed":{"name":"list_brands","description":"Lists the brands of the account, its subdivisions, each with the slug the other tools take.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List brands"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":54,"tokensAfter":54},{"name":"list_compose_drafts","fixed":{"name":"list_compose_drafts","description":"Lists the messages begun on the account addresses and never sent, last written first, with their recipients, subject, text and files. These are unsent texts, not the answers Iris wrote for review, which list_drafts holds.","inputSchema":{"type":"object","required":[],"properties":{"address":{"type":"string","description":"Narrows to the messages started on one address, from list_sender_addresses. A mailbox's own address gives all of its messages, those started under its aliases included; an alias gives the ones started under that name."}}},"annotations":{"readOnlyHint":true},"title":"List the messages started and not sent"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":165,"tokensAfter":165},{"name":"list_contacts","fixed":{"name":"list_contacts","description":"Lists the contacts of the account with their fiche, most recently seen first, and searches them by name, company or address.","inputSchema":{"type":"object","required":[],"properties":{"q":{"type":"string","description":"What to search for, matched against the name, the company and the addresses."},"limit":{"type":"integer","description":"How many to return, from 1 to 200. Defaults to 200."}}},"annotations":{"readOnlyHint":true},"title":"Search the contact book"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":122,"tokensAfter":122},{"name":"list_conversations","fixed":{"name":"list_conversations","description":"Lists threads, most recently updated first, with the contact, the subject of the mail and the one the team gave the thread (\"team_subject\", null until rename_conversation gives one), the ticket number of a helpdesk case (what the client quotes, null on somebody's mailbox), the status, where the thread stands in the pipeline, who is handling it, whether a draft is waiting for review, the folder each sits in and whether you have read it. Each thread also says since when its contact has been waitin","inputSchema":{"type":"object","required":[],"properties":{"box":{"type":"string","description":"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders."},"team":{"type":"string","description":"Narrows to the threads handed to one team, by its slug (list_teams gives it), taken by one of its members or not. Narrows the account list, so it does not go with \"box\"."},"brand":{"type":"string","description":"The slug of a brand, to narrow to that subdivision of the account: call list_brands to find it."},"limit":{"type":"integer","description":"How many threads to bring back, 1 to 200. Defaults to 100."},"before":{"type":"string","description":"Only the threads updated before this instant, as an ISO 8601 timestamp such as \"2026-08-31T09:00:00Z\". This is how you read past the first page: take the \"updated_at\" of the last thread the answer gave you and ask again with it."},"folder":{"type":"string","description":"Which folder of the box to list: one of inbox, sent, drafts, spam, trash, archive, or the id of a folder a person made (list_folders gives them). Defaults to the Inbox, like opening the mailbox does. Needs \"box\"."},"status":{"enum":["open","customer_reply","answered","delivery_failed","in_progress","closed"],"type":"string","description":"Where the thread stands: \"open\" for one nobody has taken, \"customer_reply\" when the contact has written back, \"answered\" once we replied, \"delivery_failed\" when our reply bounced, \"in_progress\" while someone works on it, \"closed\" when it is over."},"unread":{"type":"boolean","description":"Only the threads you have not read: the bold rows of the screen, and the same count its Inbox shows. Needs \"box\". A key that acts for no person has no read state and is told so rather than answered with a list built for nobody."},"channel":{"enum":["email","whatsapp","telegram","voice","agent","portal"],"type":"string","description":"The channel the thread runs on. Email is the usual one; \"portal\" carries the messages written from a client space."},"assignee":{"type":"string","description":"Narrows to the threads one person is handling, by the email address they sign in with, which list_people gives. The word \"none\" answers with what nobody has taken yet, which is the queue waiting to be shared out (a thread handed to a team has been shared out). Narrows the account list, so it does not go with \"box\"."},"external_ref":{"type":"string","description":"Narrows to the threads of one contact identified by the reference a consumer app gave them, for example \"epovest:account:42\"."}}},"annotations":{"readOnlyHint":true},"title":"List conversations"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":912,"tokensAfter":912},{"name":"list_drafts","fixed":{"name":"list_drafts","description":"Lists the answers Iris has written, with the thread each belongs to, the contact it goes to and the text as it stands. Filter on \"pending_review\" for the review queue.","inputSchema":{"type":"object","required":[],"properties":{"status":{"enum":["pending_review","sending","approved","edited","sent","rejected"],"type":"string","description":"Which drafts to list: \"pending_review\" for those awaiting a decision, \"sent\" for those that went out, \"rejected\" for those that were turned down."}}},"annotations":{"readOnlyHint":true},"title":"List drafts"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":150,"tokensAfter":150},{"name":"list_folders","fixed":{"name":"list_folders","description":"Lists the folders the people of a mailbox made in it, beside the six every mailbox has (inbox, sent, drafts, spam, trash, archive), each with its id, its name, its full path (\"Clients/LCS\") and its parent. The ids are what list_conversations, search_conversations and file_conversation take, and what update_folder and delete_folder act on.","inputSchema":{"type":"object","required":["box"],"properties":{"box":{"type":"string","description":"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders."}}},"annotations":{"readOnlyHint":true},"title":"List the folders of a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":196,"tokensAfter":196},{"name":"list_knowledge","fixed":{"name":"list_knowledge","description":"Lists the playbook docs of the account with their full content: this is the material Iris reads before drafting, and the place to look when an answer needs to say what the house does.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the knowledge docs"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":80,"tokensAfter":80},{"name":"list_mailboxes","fixed":{"name":"list_mailboxes","description":"Lists the mailboxes of the account: each one with the people who hold it, the other names that deliver into it and the storage its plan entitles the account to, which every box of it shares. It says who is on a box, never what is in one.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the mailboxes of the account"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":95,"tokensAfter":95},{"name":"list_people","fixed":{"name":"list_people","description":"Lists everyone on the account: how they sign in, the rank they hold, and how far they see into the mail. An owner and a manager work every helpdesk queue, which is said as works_every_queue; anyone else works the queues named on them and nothing else. It says who works where, never what any of it holds. A rank is not written from here: for a client of Simafri Suite it is held at the shop and restated at every sign-in.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the people of the account"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":145,"tokensAfter":145},{"name":"list_scheduled_sends","fixed":{"name":"list_scheduled_sends","description":"Lists the messages given a \"send_at\" that have not left yet, soonest first: when each leaves (in the zone of the person you act for), from which address, to whom, the subject and text, and the thread an answer goes into. A message that has left is no longer here but in its thread. One that could not leave stays, with state \"failed\" and the reason, until it is cancelled.","inputSchema":{"type":"object","required":[],"properties":{"address":{"type":"string","description":"Narrows to the messages leaving from one address, from list_sender_addresses. A mailbox's own address gives all of its messages, those leaving under its aliases included; an alias gives the ones leaving under that name."}}},"annotations":{"readOnlyHint":true},"title":"List the messages scheduled to leave later"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":209,"tokensAfter":209},{"name":"list_sender_addresses","fixed":{"name":"list_sender_addresses","description":"Lists the inbound addresses of the account, each with the block that closes what is written from it and, for a mailbox, the other names that deliver into it. Sending from any of these is what brings the answer back into the mailbox.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the addresses you can send from"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":96,"tokensAfter":96},{"name":"list_suppressed_recipients","fixed":{"name":"list_suppressed_recipients","description":"Lists the addresses that pressed \"this is spam\" on this account's mail, with the day and the label their provider gave it. The account writes to none of them, and it does so SILENTLY: a message to one of these addresses is stopped before it leaves, with no bounce and nothing in the thread to see. So this is the list to read when a mail seems to have gone nowhere and nothing said why.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the addresses the account can no longer write to"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":140,"tokensAfter":140},{"name":"list_teams","fixed":{"name":"list_teams","description":"Lists the teams of the account, the administrative team or the technical one for instance, each with its slug (what assign_conversation and the other team tools take) and who is in it. A team is a way of handing a thread to several people at once; it opens no queue, so a member only ever sees the threads of the queues they work.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"List the teams of the account"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":120,"tokensAfter":120},{"name":"mark_read","fixed":{"name":"mark_read","description":"Clears the bold on a thread for YOU, exactly as opening it on screen does: a colleague reading the same shared mailbox keeps their own. Reading a thread with get_conversation does not do this by itself, on purpose: fetching a mail is not the same as having read it. A message arriving after this call turns the thread bold again. To clear the bold on several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in \"results\" the outc","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"conversation_id":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"maxItems":50,"minItems":1}],"description":"The id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call."}}},"annotations":{"readOnlyHint":true},"title":"Mark a thread read"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":248,"tokensAfter":248},{"name":"mark_unread","fixed":{"name":"mark_unread","description":"Puts a thread back among the bold rows, for you alone: what you want to come back to. A colleague sees no change. To put several threads back among the bold rows, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in \"results\" the outcome of each thread in the order given (\"ok\", with its \"result\" or its \"error\") and counts \"succeeded\" and \"failed\". Each thread passes exactly the checks it would alone, so one refused or out of reach (\"no","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"conversation_id":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"maxItems":50,"minItems":1}],"description":"The id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Put a thread back to unread"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":252,"tokensAfter":252},{"name":"merge_conversation","fixed":{"name":"merge_conversation","description":"Merges a helpdesk ticket into another of the same contact, for the client who wrote again beside their case rather than in it. Everything it held moves to the ticket named by \"into\": its messages, their files, its notes, its drafts. Its number keeps leading to the merged case, so the client's next reply quoting it lands there. The ticket merged away is gone, a note on the one that stays says so (with your reason, when you give one in \"note\"), and a draft that was waiting on it is set aside. It c","inputSchema":{"type":"object","required":["conversation_id","into"],"properties":{"into":{"type":"string","description":"The ticket that stays: its ticket number, as list_conversations gives it in \"ticket_number\", or its conversation id."},"note":{"type":"string","description":"Optional: why both tickets are one request, for the people who work the case. It goes into the note that records the merge: do not leave a second note with add_note."},"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Merge a ticket into another"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":310,"tokensAfter":310},{"name":"poll_mailboxes","fixed":{"name":"poll_mailboxes","description":"Reads the account mailboxes right away instead of waiting for the next scheduled round, and answers with what came in. Call it when you expect a message that has not appeared yet.","inputSchema":{"type":"object","required":[],"properties":{}},"annotations":{"readOnlyHint":true},"title":"Fetch new mail now"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":79,"tokensAfter":79},{"name":"remove_mailbox_alias","fixed":{"name":"remove_mailbox_alias","description":"Stops an address delivering into a box. What already arrived through it stays in the box, and each message still says which name it came in on.","inputSchema":{"type":"object","required":["address","alias"],"properties":{"alias":{"type":"string","description":"The name to take away, from list_mailboxes."},"address":{"type":"string","description":"The address of the mailbox, for example \"marie@sonentreprise.com\": call list_mailboxes to find it. A support queue is not a mailbox: it has no holder and takes no alias."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Remove a name from a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":159,"tokensAfter":159},{"name":"remove_mailbox_holder","fixed":{"name":"remove_mailbox_holder","description":"Takes a person off a mailbox: they stop reading it from that moment. Nothing is deleted, and a box left with no holder keeps receiving and keeps everything it holds. Recorded like the other direction.","inputSchema":{"type":"object","required":["address","person"],"properties":{"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."},"address":{"type":"string","description":"The address of the mailbox, for example \"marie@sonentreprise.com\": call list_mailboxes to find it. A support queue is not a mailbox: it has no holder and takes no alias."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Take someone off a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":197,"tokensAfter":197},{"name":"remove_queue_operator","fixed":{"name":"remove_queue_operator","description":"Takes a person off a helpdesk queue: they stop seeing its threads from that moment. Nothing is deleted, and a queue nobody is named on keeps receiving and is still worked by the owners and the managers of the account.","inputSchema":{"type":"object","required":["person","queue"],"properties":{"queue":{"type":"string","description":"The address of the helpdesk queue, for example \"contact@sonentreprise.com\": call list_sender_addresses to find it. A mailbox is not a queue: it is one person's correspondence and it is handed over with add_mailbox_holder."},"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Take someone off a helpdesk queue"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":215,"tokensAfter":215},{"name":"remove_suppression","fixed":{"name":"remove_suppression","description":"Takes an address off the list above, so this account can write to them again. Weigh it before calling it: the row means a person pressed \"this is spam\" on mail from this account, and writing to them again is what turns a complaint into a sending reputation the whole platform shares. Call it when there is a reason to believe they want to hear from this account again, said by them, and not merely because a message would not leave. An address holding no suppression answers that there was nothing to","inputSchema":{"type":"object","required":["address"],"properties":{"address":{"type":"string","description":"The address to write to again, as list_suppressed_recipients gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Write to a complaining address again"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":204,"tokensAfter":204},{"name":"remove_team_member","fixed":{"name":"remove_team_member","description":"Takes a person out of a team. The threads they took from it stay on their name.","inputSchema":{"type":"object","required":["team","person"],"properties":{"team":{"type":"string","description":"The slug of the team, as list_teams gives it."},"person":{"type":"string","description":"The email address the person signs in with, which is not the same thing as the mailbox: it is how the account knows them."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Take someone out of a team"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":126,"tokensAfter":126},{"name":"rename_conversation","fixed":{"name":"rename_conversation","description":"Gives a thread a subject that says what it is about, for the people who work it: shown in the lists and on the thread screen in place of the subject of the mail, and in \"team_subject\" of list_conversations and get_conversation. It is the team's label and never the subject of the correspondent's mail: \"subject\" stays the one they wrote, every answer still leaves as a \"Re:\" of it with the ticket number, and their mail client keeps the case as one conversation. Use it on a ticket whose subject says","inputSchema":{"type":"object","required":["conversation_id","team_subject"],"properties":{"team_subject":{"type":"string","description":"The subject the team gives the thread, plain text on one line, up to 255 characters: what is asked, for example \"Devis pour un site vitrine\" rather than \"Nouveau message de Jessica\"."},"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Give a thread a subject of the team's own"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":277,"tokensAfter":277},{"name":"rename_team","fixed":{"name":"rename_team","description":"Gives a team a new name. Its slug stays, so every reference to it keeps working.","inputSchema":{"type":"object","required":["team","name"],"properties":{"name":{"type":"string","description":"Its new name, 1 to 80 characters."},"team":{"type":"string","description":"The slug of the team, as list_teams gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Rename a team"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":99,"tokensAfter":99},{"name":"search_conversations","fixed":{"name":"search_conversations","description":"Finds the threads of one mailbox by their subject, their text, the people on them or the names of the files they carried, best answer first. Call list_sender_addresses to find the box. This is how you look a mail up when you know a word of it and not where it is.","inputSchema":{"type":"object","required":["box","q"],"properties":{"q":{"type":"string","description":"What is being looked for. Plain words are all required, \"a phrase in quotes\" is looked for as written, \"or\" offers an alternative and a leading \"-\" excludes a word."},"box":{"type":"string","description":"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders."},"limit":{"type":"integer","description":"How many threads to bring back, 1 to 200. Defaults to 100."},"folder":{"type":"string","description":"Narrows to one folder of the box: one of inbox, sent, drafts, spam, trash, archive, or the id of a folder a person made (list_folders gives them). Left out, the whole box is searched, which is usually what is wanted: a mail is looked for precisely because nobody remembers where it was filed."}}},"annotations":{"readOnlyHint":true},"title":"Search a mailbox"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: true (inferred from the name).","verify":true}],"tokensBefore":357,"tokensAfter":357},{"name":"send_email","fixed":{"name":"send_email","description":"Writes and sends an email to someone, and opens the thread their answer will land in. The text goes out as given, so this is the tool for a message a person has read and approved. With \"send_at\" it is scheduled instead: nothing leaves until then, and list_scheduled_sends shows it waiting.","inputSchema":{"type":"object","required":["from","to","subject","body"],"properties":{"cc":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"Who else receives it, in copy. Everyone on the mail sees these."},"to":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"Who it is written to. The thread is filed under the first of them."},"bcc":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"Who else receives it without the others being told. A blind copy is kept on the sending alone: the thread records the visible recipients only."},"body":{"type":"string","description":"The text of the message, as the contact will read it. Plain text, in their language."},"from":{"type":"string","description":"The address to send from: one of the account inbound addresses, or one of the other names of a mailbox, which is what brings the answer back into that mailbox. Call list_sender_addresses to find them, aliases included."},"send_at":{"type":"string","description":"When it should leave, if not now: a date and time with its offset, such as \"2026-10-12T08:30:00+03:00\", at most a year ahead. Without an offset it is read in the zone of the person this connection acts for. Left out, it leaves at once."},"subject":{"type":"string","description":"The subject line, up to 255 characters."},"attachments":{"type":"array","items":{"type":"object","properties":{"filename":{"type":"string","description":"The name the recipient sees, extension included. Inline form only."},"upload_id":{"type":"string","description":"A file already sent to its upload address, as create_attachment_upload gives it. The other fields are then left out: the name and the media type are the ones the slot was opened with."},"content_type":{"type":"string","description":"The media type, for example \"application/pdf\". Derived from the name when left out."},"content_base64":{"type":"string","description":"The file itself, base64 encoded. Inline form only, and only worth it for something small."}}},"description":"Files to send along, up to 10 and 7 MiB in total. Each one is named EITHER by \"upload_id\", a file already pushed to a slot from create_attachment_upload, OR inline by \"filename\" and \"content_base64\". Prefer the upload for anything but a few lines of text: a file written out as base64 has to be produced character by character, which a real document overruns long before the 7 MiB cap."},"contact_name":{"type":"string","description":"The name of the recipient, recorded on their fiche when we open one."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Send a new email"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":818,"tokensAfter":818},{"name":"set_archive_on_reply","fixed":{"name":"set_archive_on_reply","description":"Says whether a thread of a mailbox leaves the Inbox for the Archive as soon as the box answers it, whether the answer is written in the webmail, through these tools or in a mail app such as Thunderbird. The thread comes back to the Inbox when a new message arrives in it. A setting of the box: on a box held by several people it moves the thread for all of them. A helpdesk queue refuses it, its threads being worked by status.","inputSchema":{"type":"object","required":["address","archive_on_reply"],"properties":{"address":{"type":"string","description":"The mailbox, from list_sender_addresses."},"archive_on_reply":{"type":"boolean","description":"True to archive answered threads, false to leave them in the Inbox."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true},"title":"Archive a thread once it is answered"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":215,"tokensAfter":215},{"name":"set_auto_draft","fixed":{"name":"set_auto_draft","description":"Says whether an incoming message has Iris draft an answer on its own. With it off, a draft is written when someone asks for one from the inbox, which is what keeps the model spend where you put it.","inputSchema":{"type":"object","required":["auto_draft"],"properties":{"auto_draft":{"type":"boolean","description":"true has every incoming message drafted, false leaves the drafting to a person, from the inbox."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Set automatic drafting"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":127,"tokensAfter":127},{"name":"set_conversation_status","fixed":{"name":"set_conversation_status","description":"Says where a thread stands, and optionally where it stands in the pipeline. Both are recorded as decided by a person, so a later reading by Iris keeps them. To set the same status on several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in \"results\" the outcome of each thread in the order given (\"ok\", with its \"result\" or its \"error\") and counts \"succeeded\" and \"failed\". Each thread passes exactly the checks it would alone","inputSchema":{"type":"object","required":["conversation_id","status"],"properties":{"status":{"enum":["open","customer_reply","answered","delivery_failed","in_progress","closed"],"type":"string","description":"Where the thread stands: \"open\" for one nobody has taken, \"customer_reply\" when the contact has written back, \"answered\" once we replied, \"delivery_failed\" when our reply bounced, \"in_progress\" while someone works on it, \"closed\" when it is over."},"deal_stage":{"type":"string","description":"Where the thread stands in the pipeline, in your own vocabulary, up to 128 characters. An empty string clears it."},"conversation_id":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"maxItems":50,"minItems":1}],"description":"The id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Set the status of a conversation"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":409,"tokensAfter":409},{"name":"set_signature","fixed":{"name":"set_signature","description":"Writes the block that closes what is written from an address. It belongs to the address, so everyone who writes from it signs the same way; it is put into a message when one is being written, not added behind the sender back.","inputSchema":{"type":"object","required":["address","signature"],"properties":{"address":{"type":"string","description":"The address to sign for, from list_sender_addresses."},"signature":{"type":"string","description":"The signature itself, plain text, up to 2000 characters. An empty text removes it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Set the signature of an address"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":160,"tokensAfter":160},{"name":"unblock_sender","fixed":{"name":"unblock_sender","description":"Lets an address write to the Inbox again: their next message is filed like anybody else's. Threads already sitting in Spam stay where they are, a block having always been about the mail still to come; file_conversation with \"inbox\" is what brings one of them back. An address this account holds no block on answers that there was nothing to lift.","inputSchema":{"type":"object","required":["address"],"properties":{"address":{"type":"string","description":"The address to unblock, as list_blocked_senders gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false},"title":"Unblock a sender"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":157,"tokensAfter":157},{"name":"unsubscribe","fixed":{"name":"unsubscribe","description":"Leaves the mailing list a thread came from (a newsletter, a promotional mailing, a notification list), in the name of the mailbox it arrived in, with what the last message received in the thread offers: one POST to the list's unsubscribe address when it accepts a one-click unsubscription, otherwise a short mail from the box to the list's own address. get_conversation says, in \"unsubscribe\" on each message, whether it offers a way out (\"one_click\", \"mailto\") and when the box took it (\"done_at\"). ","inputSchema":{"type":"object","required":["conversation_id"],"properties":{"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false},"title":"Unsubscribe from a mailing list"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: true, idempotentHint: false (inferred from the name).","verify":true}],"tokensBefore":205,"tokensAfter":205},{"name":"update_contact","fixed":{"name":"update_contact","description":"Writes the fiche fields you pass, and leaves the others as they are. What is written here is recorded as coming from a person, which keeps a later reading by Iris from overwriting it.","inputSchema":{"type":"object","required":["contact_id"],"properties":{"name":{"type":"string","description":"The name of the person."},"phone":{"type":"string","description":"Their phone number, as they gave it."},"sector":{"type":"string","description":"The sector they work in."},"address":{"type":"string","description":"Their postal address."},"language":{"type":"string","description":"The language to write to them in, as a code such as \"fr\", \"en\" or \"mg\"."},"contact_id":{"type":"string","description":"The id of the contact, as list_contacts gives it."},"company_name":{"type":"string","description":"The company they write for."},"project_type":{"type":"string","description":"What they came for."},"contact_title":{"type":"string","description":"Their role there, for example \"Directrice generale\"."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Enrich a contact fiche"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":291,"tokensAfter":291},{"name":"update_folder","fixed":{"name":"update_folder","description":"Renames a folder a person made, moves it under another one or to the top, or both; the folders under it follow, and the threads in it stay. What you leave out keeps its value.","inputSchema":{"type":"object","required":["folder_id"],"properties":{"name":{"type":"string","description":"Its new name."},"folder_id":{"type":"string","description":"The folder, by its id from list_folders."},"parent_id":{"type":["string","null"],"description":"The folder it moves under, or null for the top."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Rename or move a folder"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":149,"tokensAfter":149},{"name":"update_knowledge","fixed":{"name":"update_knowledge","description":"Writes a doc whole, keeping the previous version dated in its history. Send the title and the content each time, plus the brands and addresses it applies to.","inputSchema":{"type":"object","required":["doc_id","title","content"],"properties":{"title":{"type":"string","description":"The title of the doc, unique in the account."},"brands":{"type":"array","items":{"type":"string"},"description":"The brand slugs this doc applies to, from list_brands. An empty list applies it to the whole account."},"doc_id":{"type":"string","description":"The id of the doc, as list_knowledge gives it."},"content":{"type":"string","description":"The doc itself, in Markdown. This is the text Iris reads before drafting."},"addresses":{"type":"array","items":{"type":"string"},"description":"The inbound addresses this doc applies to, from list_sender_addresses. An empty list applies it to every address of the brands above."},"sort_order":{"type":"integer","description":"Where the doc sits in the reading order, lowest first."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Rewrite a knowledge doc"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":295,"tokensAfter":295},{"name":"update_note","fixed":{"name":"update_note","description":"Replaces the text of an internal note left on a thread, for a typo, a wrong figure or a word that no longer holds. The note keeps its author, its place and its files, and shows it was corrected (\"updated_at\" in get_conversation). Allowed to the author of the note and to a manager or the owner of the account; anyone else is refused. Same rules on the text as add_note: plain text, up to 10000 characters. The note is named by its id, as \"notes\" of get_conversation gives it.","inputSchema":{"type":"object","required":["conversation_id","note_id","body"],"properties":{"body":{"type":"string","description":"The new text of the note, plain text, up to 10000 characters."},"note_id":{"type":"string","description":"The id of the note, as \"notes\" of get_conversation gives it."},"conversation_id":{"type":"string","description":"The id of the conversation, as list_conversations gives it."}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true},"title":"Correct an internal note"},"changes":[{"kind":"annotations","detail":"Added readOnlyHint: false, destructiveHint: false, idempotentHint: true (inferred from the name).","verify":true}],"tokensBefore":260,"tokensAfter":260}],"toolsChanged":62,"tokensSaved":0,"todo":[],"note":"Deterministic fixes. Changes marked verify need a human look before shipping (renames, inferred annotations, inferred types, removed text). Parameter descriptions in `todo` need to be written by someone who knows the API."}