com.sonarconnections/sonar-connections

Est-ce que com.sonarconnections/sonar-connections est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.sonarconnections/sonar-connections » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 55 outils

• biz_availability≈ 378 tokens

  Open appointment slots at a business served through this connector, for one date (default today in its own timezone). Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice). Reachable here but not through this tool: Long Beach Brunch Bakehouse (longbeachbrunch), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no bookings. Each slot has a stable `slotId` that biz_book accepts; started slots are never returned. A closed day returns none with a reason. closedReason HOURS_UNSTATED is NOT a closed day: say the business has not published hours for that date, never that it is closed.

  Paramètres, retour & exemple (3)

  Paramètres

  • date · string · optionnel
    YYYY-MM-DD, defaults to today in the business timezone
  • business · string · optionnel
    Which business, by name or id. Available: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental). Optional, defaults to velvetandclay. An unclear name is REFUSED with the list, not answered about a different business.
  • businessId · string · optionnel
    Alias for `business`; ignored when `business` is given.

  Exemple d'appel

  {"name": "biz_availability", "arguments": {"date": "texte", "business": "texte", "businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• biz_info≈ 650 tokens

  Details for a business served through this connector: tagline, services or menu with prices, weekly hours and today's hours. Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice), Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar), Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). Speak `hoursNow.text`, resolved in the business's own timezone. `openToday` is true, false or NULL; NULL IS NOT FALSE: when `hoursState` is 'unstated' say the hours are not published and NEVER say it is closed. A `schedulingSystem` of Square means bookings live in that business's own Square calendar. `isDemo` says whether it is a demonstration. For what a shop sells call biz_storefront; to book, biz_availability then biz_book.

  Paramètres, retour & exemple (2)

  Paramètres

  • business · string · optionnel
    Which business, by name or id. Available: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Long Beach Brunch Bakehouse (longbeachbrunch), Make Collectives (makecollectives), Kristin Dunn Bookbinding and Design (kdbooks). Optional, defaults to velvetandclay. An unclear name is REFUSED with the list, not answered about a different business.
  • businessId · string · optionnel
    Alias for `business`; ignored when `business` is given.

  Exemple d'appel

  {"name": "biz_info", "arguments": {"business": "texte", "businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "found": true, "isDemo": true, "message": "texte", "bookable": true, "business": {}, "hoursNow": {}, "servedBy": "texte", "available": [], "openToday": true, "sourceUrl": "texte", "businessId": "texte"}}

• biz_menu≈ 658 tokens

  The PICKUP MENU for a business served through this connector: items, prices, allergens, notice needed, and the pickup windows on a date (default today). Businesses with a pickup menu here: Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) have no pickup menu here. longbeachbrunch sells cookies, bars, pastry, brunch boxes, platters, cakes and coffee. This tool only reads. Orders are placed with a separate tool, biz_order, which takes item ids and a pickup window id from this reply exactly as written; right now it takes pickup orders for Long Beach Brunch Bakehouse (longbeachbrunch). Pickup only. An 'unstated' `hoursByDay` row is NEVER spoken as closed.

  Paramètres, retour & exemple (3)

  Paramètres

  • date · string · optionnel
    Optional YYYY-MM-DD; today in the business timezone.
  • business · string · optionnel
    Which business, by name or id. Available: Long Beach Brunch Bakehouse (longbeachbrunch). The default (velvetandclay) has no pickup menu here, so NAME THE BUSINESS: an omitted argument is refused. An unclear name is REFUSED with the list, not answered about a different business.
  • businessId · string · optionnel
    Alias for `business`; ignored when `business` is given.

  Exemple d'appel

  {"name": "biz_menu", "arguments": {"date": "texte", "business": "texte", "businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "open": true, "error": "texte", "found": true, "notes": [], "isDemo": true, "message": "texte", "servedBy": "texte", "available": [], "sourceUrl": "texte", "businessId": "texte", "categories": []}}

• biz_order≈ 535 tokens

  Places a pickup pre-order at a business served through this connector: placing an order, a pickup order, or the checkout after biz_menu. Needs `items` and a `pickupWindowId` from biz_menu and the collector's first name; no phone, email, surname or card is collected. Businesses served here: Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no pickup orders. Most orders are paid at pickup; where the reply is HELD, its `payUrl` is the only payment link this connector issues: give it exactly as returned. `isDemo` true reserves nothing.

  Paramètres, retour & exemple (6)

  Paramètres

  • note · string · optionnel
    Optional note, 140 characters; contact details are removed.
  • items · array · requis
    Order lines, at least one.
  • business · string · optionnel
    Which business, by name or id. Available: Long Beach Brunch Bakehouse (longbeachbrunch). The default (velvetandclay) takes no pickup orders, so NAME THE BUSINESS: an omitted argument is refused. An unclear name is REFUSED with the list, not answered about a different business.
  • firstName · string · requis
    First name only.
  • businessId · string · optionnel
    Alias for `business`; ignored when `business` is given.
  • pickupWindowId · string · requis
    Window id from biz_menu.

  Exemple d'appel

  {"name": "biz_order", "arguments": {"items": [], "firstName": "texte", "pickupWindowId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• biz_order_status≈ 242 tokens

  Read the CURRENT state of a pickup order placed through this connector, by its confirmation code (the LBB-XXXXXX style code biz_order returned). It answers with the order state, the payment state, whether it is PAID, the pickup window, the business name and the total, and nothing else: no customer name, no items and no payment link. Use it after a customer has been sent to a checkout page, to tell them whether the payment has landed and the order is placed. It changes nothing. A code that names no order comes back not found.

  Paramètres, retour & exemple (1)

  Paramètres

  • confirmationCode · string · requis
    The order confirmation code, e.g. LBB-KKA8Y2. Case does not matter.

  Exemple d'appel

  {"name": "biz_order_status", "arguments": {"confirmationCode": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• biz_set_item_availability≈ 380 tokens

  Marks one item on a business menu as sold out for today, or puts it back on. Needs a personal connector token, `business`, `soldOut`, and `itemId` or `itemName`. Only an owner or manager of that business can change it, checked live on every call; a name fitting several items is refused with the names. It works in two steps: a call without `confirm` returns a preview and a `confirmToken` and changes nothing; a call with confirm true and that token makes the change.

  Paramètres, retour & exemple (7)

  Paramètres

  • itemId · string · optionnel
    The item id from biz_menu.
  • confirm · boolean · optionnel
    Absent on the first call, which changes nothing; true with confirmToken makes the change.
  • soldOut · boolean · requis
    true marks it sold out today; false puts it back.
  • business · string · requis
    The business by name or id, as biz_menu returned it.
  • itemName · string · optionnel
    Or the item name.
  • requestId · string · optionnel
    Optional caller id, 8 or more characters; a repeat returns the first result.
  • confirmToken · string · optionnel
    The token the first call returned.

  Exemple d'appel

  {"name": "biz_set_item_availability", "arguments": {"soldOut": true, "business": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• biz_storefront≈ 613 tokens

  CALL THIS for what a shop sells, its products, its prices, a gift idea, or browsing or shopping a store served here. Reads that shop's OWN published catalog: title, maker, type, price, stock and one image per product. Businesses served here: Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental) and Long Beach Brunch Bakehouse (longbeachbrunch) publish no shop catalog we read. makecollectives is Make Collectives, a boutique at 430 E. 1st St in Long Beach. kdbooks is Kristin Dunn Bookbinding and Design in Long Beach; her work is MADE TO ORDER, so say what `leadTimeNote` says. TWO SHOP PLATFORMS ARE READ HERE, a Shopify store and a WooCommerce shop, same reply shape; ON A WOOCOMMERCE SHOP ONE CART LINK CARRIES EXACTLY ONE ITEM. `query` only removes products. Sixty a page with `pageCount` and `total`: never say sixty is all. Give `cartUrl` and `shopUrl` exactly as returned, never a link of your own. WHERE THIS REPLY DRAWS THE SHOP CARD, THE CARD ITSELF HOLDS A BASKET: the person taps Add to cart there. Say what `buyingNote` says. No payment passes through Sonar Connections.

  Paramètres, retour & exemple (5)

  Paramètres

  • page · integer · optionnel
    Optional page, 1-based; 60 products a page.
  • limit · integer · optionnel
    Optional, 1 to 60.
  • query · string · optionnel
    Optional words to narrow the catalog; it only removes products.
  • business · string · optionnel
    Which business, by name or id. Available: Make Collectives (makecollectives), Kristin Dunn Bookbinding and Design (kdbooks). The default (velvetandclay) publishes no shop catalog we read, so NAME THE BUSINESS: an omitted argument is refused. An unclear name is REFUSED with the list, not answered about a different business.
  • businessId · string · optionnel
    Alias for `business`; ignored when `business` is given.

  Exemple d'appel

  {"name": "biz_storefront", "arguments": {"page": 1, "limit": 1, "query": "texte", "business": "texte", "businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• booth_claim_swag≈ 550 tokens

  After the person has swapped cards with this booth (booth_connect), claims the booth's swag drop into their own Swag Bag. Pass `eventId` and `boothId` as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no swag on offer now is refused with UNKNOWN_UNLOCK. Swag already in their bag is not claimed twice: the reply says already. Returns ok, the drop's `id`, `done` and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no `confirm` returns a `confirmToken` and changes nothing; a call with confirm true and that token applies it.

  Paramètres, retour & exemple (4)

  Paramètres

  • boothId · string · requis
    The booth id, as booth_connect was given it.
  • confirm · boolean · optionnel
    Absent on the first call, which changes nothing. true, together with confirmToken, applies it.
  • eventId · string · requis
    The event id or public slug the booth is at.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "booth_claim_swag", "arguments": {"boothId": "texte", "eventId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "code": "texte", "done": true, "edit": {}, "kind": "drop", "booth": "texte", "error": "texte", "title": "texte", "already": true, "message": "texte", "preview": true}}

• booth_connect≈ 546 tokens

  Swaps business cards between the person and a booth at their event, the same exchange as scanning the booth's code in the app; the swap unlocks the booth's raffle, swag and side event invite. Pass `eventId` and the `boothId` from an events_booths row. Needs a personal connector token and a seat at the event. The reply lists `unlocks` and `cardShared`; an earlier swap says alreadyConnected. Two steps: without `confirm` it returns a `confirmToken` and shares nothing; with confirm true and that token it shares. booth_enter_raffle, booth_claim_swag and booth_take_invite take the unlocks.

  Paramètres, retour & exemple (4)

  Paramètres

  • boothId · string · requis
    The booth id from an events_booths row, as that row gives it.
  • confirm · boolean · optionnel
    Absent on the first call, which shares nothing. true, together with confirmToken, swaps the cards.
  • eventId · string · requis
    The event id or public slug the booth is at.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "booth_connect", "arguments": {"boothId": "texte", "eventId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "edit": {}, "booth": "texte", "error": "texte", "message": "texte", "preview": true, "unlocks": [], "servedBy": "texte", "connected": true, "cardShared": "texte", "confirmToken": "texte"}}

• booth_enter_raffle≈ 548 tokens

  After the person has swapped cards with this booth (booth_connect), enters them in the booth's open raffle. Pass `eventId` and `boothId` as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no open raffle is refused with UNKNOWN_UNLOCK. A raffle they are already in is not entered twice: the reply says already. Returns ok, the raffle's `id`, `done` and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no `confirm` returns a `confirmToken` and changes nothing; a call with confirm true and that token applies it.

  Paramètres, retour & exemple (4)

  Paramètres

  • boothId · string · requis
    The booth id, as booth_connect was given it.
  • confirm · boolean · optionnel
    Absent on the first call, which changes nothing. true, together with confirmToken, applies it.
  • eventId · string · requis
    The event id or public slug the booth is at.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "booth_enter_raffle", "arguments": {"boothId": "texte", "eventId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "code": "texte", "done": true, "edit": {}, "kind": "raffle", "booth": "texte", "error": "texte", "title": "texte", "already": true, "message": "texte", "preview": true}}

• booth_set_away≈ 453 tokens

  Marks a booth the person staffs as stepped away, or back; attendees looking at that booth see the presence change. Needs a personal connector token (a shared token reads but changes nothing), `eventId`, `boothId` and `away`. Only a booth the person owns, administers or staffs at that event can be changed, checked against live records on every call. It works in two steps: a call without `confirm` returns a preview of exactly what will change, plus a `confirmToken`, and changes nothing; a call with confirm true and that token makes the change. The token lasts two minutes, works once, and stops working if any argument changes.

  Paramètres, retour & exemple (6)

  Paramètres

  • away · boolean · requis
    true to mark the booth stepped away, false to mark it back.
  • boothId · string · requis
    The booth id, exactly as events_booths returned it. Not the booth name.
  • confirm · boolean · optionnel
    Absent on the first call, which changes nothing. true, together with confirmToken, makes the change.
  • eventId · string · requis
    The event the booth is at, exactly as events_list returned it.
  • requestId · string · optionnel
    An id for this change chosen by the caller, at least 8 characters. A repeat with the same id and the same arguments returns the first result without changing anything a second time.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "booth_set_away", "arguments": {"away": true, "boothId": "texte", "eventId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• booth_take_invite≈ 569 tokens

  After the person has swapped cards with this booth (booth_connect), takes the invite to the booth's side event for them; the invite lands in their own inbox. Pass `eventId` and `boothId` as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no side event open to invites is refused with UNKNOWN_UNLOCK. An invite they already hold is not sent twice: the reply says already. Returns ok, the side event's `id`, `done` and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no `confirm` returns a `confirmToken` and changes nothing; a call with confirm true and that token applies it.

  Paramètres, retour & exemple (4)

  Paramètres

  • boothId · string · requis
    The booth id, as booth_connect was given it.
  • confirm · boolean · optionnel
    Absent on the first call, which changes nothing. true, together with confirmToken, applies it.
  • eventId · string · requis
    The event id or public slug the booth is at.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "booth_take_invite", "arguments": {"boothId": "texte", "eventId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "code": "texte", "done": true, "edit": {}, "kind": "satellite_invite", "booth": "texte", "error": "texte", "title": "texte", "already": true, "message": "texte", "preview": true}}

• event_accept≈ 450 tokens

  Accepts a hello the person has received, which opens a conversation with the person who sent it. Needs a personal connector token and the hello as `firstName` (as an event_requests row spelled it) or `requestId` (as that row gave it). It accepts only hellos addressed to the caller; the server checks this and refuses with NOT_RECEIVER otherwise. A `firstName` that matches two waiting hellos returns AMBIGUOUS_NAME and accepts nothing. Accepting twice changes nothing. Returns ok:true when the conversation is open; event_inbox reads it and event_reply answers in it.

  Paramètres, retour & exemple (2)

  Paramètres

  • firstName · string · optionnel
    Optional. The first name as an event_requests row spelled it, matched against the caller's own pending hellos only. Two matches return AMBIGUOUS_NAME and nothing is accepted.
  • requestId · string · optionnel
    Optional. The requestId as an event_requests row gave it. When both this and firstName are sent, this one is used.

  Exemple d'appel

  {"name": "event_accept", "arguments": {"firstName": "texte", "requestId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": "texte", "chatId": "texte", "message": "texte", "requests": [], "servedBy": "texte", "candidates": []}}

• event_card_links≈ 518 tokens

  Lists the business cards the person received in swaps at an event (a booth scan or a badge swap, in either direction), newest first, at most 50. Each row has the other person's first name, their company, where and when they met (`metAt`), their LinkedIn link when their card carries one (`linkedin` with `url` and `deepLink`, otherwise null), whether the card has an email or a phone (yes or no; the values are not included), and `note`, a one-line "we met at" sentence for a LinkedIn invitation. The same list also comes as a numbered text block, one line per person with the link. LinkedIn does not let other apps send invitations, so the person opens each link and sends the invitation in LinkedIn. Needs a personal connector token. The event is `eventIdOrSlug` when given, otherwise the person's current event, otherwise every swap they have. It only reads; event_card_save_linkedin keeps the person's own LinkedIn link on their card.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrSlug · string · optionnel
    Optional event id, slug or name; else the current event, else every swap.

  Exemple d'appel

  {"name": "event_card_links", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "cards": [], "count": 1, "error": "texte", "shown": 1, "eventId": "texte", "hasMore": true, "message": "texte", "servedBy": "texte", "withLinkedin": 1, "ownCardHasLinkedin": true}}

• event_card_save_linkedin≈ 536 tokens

  Keeps the person's own LinkedIn profile link (`myLinkedin`, a linkedin.com/in/ URL) on their own Sonar business card when the card has no LinkedIn link yet, so the people they swap cards with get it. Needs a personal connector token. A card that already carries this link stays as it is and the reply says already saved; a card that carries a different link keeps it (DIFFERENT_ON_FILE), and that link is changed in the Sonar app profile. Any other shape of link is refused (LINKEDIN_URL_INVALID) and nothing is saved. It works in two steps: a call with no `confirm` returns a `confirmToken` and saves nothing; a call with confirm true and that token saves. It changes only the person's own card. Returns ok, `outcome` and a sentence for the person.

  Paramètres, retour & exemple (3)

  Paramètres

  • confirm · boolean · optionnel
    Absent on the first call, which saves nothing. true, together with confirmToken, saves the link.
  • myLinkedin · string · requis
    The person's own LinkedIn profile link, a linkedin.com/in/ URL. Kept on their own card when the card has no LinkedIn link yet.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "event_card_save_linkedin", "arguments": {"myLinkedin": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "edit": {}, "error": "texte", "message": "texte", "outcome": "texte", "linkedin": "texte", "servedBy": "texte", "confirmToken": "texte", "expiresInSeconds": 1}}

• event_change_detail≈ 522 tokens

  THE HOSTS' OWN EDIT of a wedding or other personal event. IT APPLIES THE CHANGE ON THIS CALL, one `field` per call, and the reply says the detail now and before: read both out. A time needs am or pm, or a 24 hour time that reads one way; a bare "4:30" is refused. For faq_answer, `question` adds the entry or replaces its answer. Every change is logged and can be read back; event_change_undo reverses the caller's own latest one. Only the hosts can change it; read refusals (NOT_A_HOST, BAD_TIME, NO_SUCH_PLACE, NO_SUCH_ENTRY, NO_CHANGE) out as given; it sends no message and it changes nothing else on the event; the event's Wallet passes are updated with the new detail as a lock-screen notice and the reply's `passNotice` says how many passes were reached. Needs a personal connector token.

  Paramètres, retour & exemple (6)

  Paramètres

  • field · string · requis · ceremony_time | ceremony_place | reception_time | reception_place | dress_code | arrival_note | schedule_time | faq_answer
    Which detail. The place fields take an optional `venueName`; schedule_time takes `entryTitle`; faq_answer takes `question`.
  • value · string · requis
    The new value, as the hosts say it: a time, a place, a sentence or an answer. No links or markup.
  • question · string · optionnel
    For faq_answer: the question.
  • venueName · string · optionnel
    Optional venue name, for the place fields.
  • entryTitle · string · optionnel
    For schedule_time: the row title as spelled.
  • eventIdOrName · string · requis
    The event id or the event name as the hosts spell it.

  Exemple d'appel

  {"name": "event_change_detail", "arguments": {"field": "ceremony_time", "value": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_change_undo≈ 327 tokens

  Reverses the caller's own most recent change to a wedding or other personal event they host, restoring the value the detail had before it, through the same checks and into the same change log; each further call reverses the next older change of theirs. Needs a personal connector token and `eventIdOrName`. Only the hosts can use it, and only on changes they made themselves; an undo is not itself reversed. A change that gave a detail its first value, or no change left to reverse, answers NOTHING_TO_UNDO and changes nothing. When the event's Wallet passes are switched on, restoring a detail the pass shows updates every pass of the event and pushes the restored line to each phone that registered it. Returns the detail, the value before and after, a sentence for the person and, with passes on, `passNotice`.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrName · string · requis
    REQUIRED. The event id (test_wedding_a_garden) or the event NAME as the hosts spell it ("Susie and John").

  Exemple d'appel

  {"name": "event_change_undo", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_find_matches≈ 368 tokens

  Lists the people at an event the person has joined whose stated intent fits theirs. Needs a personal connector token; the event is `eventId` or the current one. Each row carries a first name, intent, who they are looking for, their booth if a vendor, `fit` and `why`. No row carries a phone number, email address, surname, account id or photo. Only people who chose to be findable are listed, at most 20, ordered best fit first by what each person wrote on their badge; two buyers whose lines agree are matches for each other. `fit` is one of three words: "strong" (most of what the caller declared is echoed on the other side), "good" (a real overlap) or "some" (a reason to be on the list and no more). `why` is one sentence written by the server naming the shared words, or the topic both wrote about. The reply carries no score, percentage, rating or rank. With no intent set the reply has `needsIntent` and no rows. An empty reply carries `emptyReason` and a plain `message` (none_findable, none_present, event_not_live or no_text_match).

  Paramètres, retour & exemple (1)

  Paramètres

  • eventId · string · optionnel
    Optional. An event the person has joined. When absent, the event the person is currently in.

  Exemple d'appel

  {"name": "event_find_matches", "arguments": {"eventId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_guest_request_handled≈ 306 tokens

  Marks one guest request on a wedding or other personal event the caller hosts as handled, which takes it off the hosts' open list (event_guest_requests). Needs a personal connector token, `eventIdOrName` and `requestId`, the `id` of a row event_guest_requests returned. It records who marked it and when, messages nobody and changes nothing on the event. A request already marked handled stays handled and the reply says already. Only the hosts can mark one; an id that is not a request on this event is refused with NO_SUCH_REQUEST. Returns ok, the request `id`, `handled` and `already`.

  Paramètres, retour & exemple (2)

  Paramètres

  • requestId · string · requis
    REQUIRED. The `id` of one request, exactly as a row from event_guest_requests gives it.
  • eventIdOrName · string · requis
    REQUIRED. The event id or the event NAME as the hosts spell it.

  Exemple d'appel

  {"name": "event_guest_request_handled", "arguments": {"requestId": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_guest_requests≈ 320 tokens

  THE HOSTS' OWN LIST of what their guests have asked for on a personal event this connector serves. Call it for "what have our guests asked for", "any dietary requests", "who needs anything". It returns the OPEN requests, newest first, each one as a category, the note the guest wrote, who it is from and when it landed. ONLY THE HOSTS can read it; anybody else gets a refusal you read out as given. WHO IT IS FROM IS A FIRST NAME OR THE WORDS "a guest", and there is no phone number, no email address and no account id on this surface at all, so never offer to contact somebody from this list. Read the notes out as given and do not summarise a need into something the guest did not say. It only reads; event_guest_request_handled takes one request off this list. It requires a personal connector token.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrName · string · requis
    REQUIRED. The event id or the event NAME as the hosts spell it.

  Exemple d'appel

  {"name": "event_guest_requests", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_inbox≈ 458 tokens

  Reads the person's own conversations with people they connected with at an event. Needs a personal connector token. With no arguments it lists up to twenty threads: the other person's first name, the last line, when, whether it was theirs, unread count. With `firstName` or `chatId` it returns that conversation's last lines. No row carries a phone number, email address, surname, account id or photo. Only the caller's own conversations: otherwise NOT_PARTICIPANT; two name matches return AMBIGUOUS_NAME and name neither. It only reads and marks nothing read.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · number · optionnel
    Optional lines of one conversation, at most 50 (default 30).
  • chatId · string · optionnel
    Optional conversation id from a thread row.
  • firstName · string · optionnel
    Optional first name from a thread row.

  Exemple d'appel

  {"name": "event_inbox", "arguments": {"limit": 1, "chatId": "texte", "firstName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": "texte", "chatId": "texte", "unread": 1, "message": "texte", "threads": [], "messages": [], "returned": 1, "servedBy": "texte", "candidates": []}}

• event_meetup_announce≈ 674 tokens

  Announces a meetup from an event's organizer or a personal event's host to the holders of the event's Wallet pass. Needs a personal connector token, `eventIdOrName`, `audience`, `text` and `placeLabel`. `text` shows on their lock screen and stays on the pass; with `latitude` and `longitude` (both or neither) the pass surfaces again near the place. The reply's `noticeId` names the meetup. Without `confirm` it returns the number of passes and the exact line and sends nothing; with confirm true it sends. Only the hosts or the organizer can send. "my_booth" returns VENDOR_OFF. Six an hour per event, shared with event_pass_notice, then RATE_LIMITED.

  Paramètres, retour & exemple (15)

  Paramètres

  • at · string · optionnel
    Optional time, with a time zone.
  • text · string · requis
    One plain line, up to 120 characters. No links or markup.
  • tier · string · optionnel
    general, vendor or host.
  • intent · string · optionnel
    Buyer, Vendor, Networker or Social.
  • boothId · string · optionnel
    The booth id.
  • confirm · boolean · optionnel
    Absent previews; true sends.
  • serials · array · optionnel
    Up to fifty pass serials.
  • audience · string · requis · everyone | tier | intent | serials | booth | meetup_yes | meetup_no | my_booth
    everyone, tier, intent, serials, booth, meetup_yes or meetup_no.
  • latitude · number · optionnel
    Optional latitude.
  • noticeId · string · optionnel
    The earlier meetup noticeId.
  • longitude · number · optionnel
    Optional longitude.
  • requestId · string · optionnel
    Optional caller id; one id sends once.
  • placeLabel · string · requis
    The name of the place.
  • relevantText · string · optionnel
    Optional line shown near the place. Default: "Sonar meetup inside, show this pass."
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "event_meetup_announce", "arguments": {"text": "texte", "audience": "everyone", "placeLabel": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_meetup_rsvp≈ 339 tokens

  Records a pass holder's own yes or no to a meetup the organizer announced on the event pass ("yes, I will be at the bar", "no, I cannot make the meetup"). Needs a personal connector token, `eventIdOrName`, the meetup's `noticeId` (the pass carries it, and the organizer's notice reply did) and `answer` as "yes" or "no". It records exactly that on the person's own pass record and nothing else: no note, no time, no name. The organizer can then send a notice to everybody who said yes. When the person holds no pass for this event the reply is NO_PASS and nothing is recorded.

  Paramètres, retour & exemple (3)

  Paramètres

  • answer · string · requis · yes | no
    REQUIRED. "yes" they are coming, "no" they are not. Nothing else is recorded.
  • noticeId · string · requis
    REQUIRED. The noticeId of the meetup notice being answered, as the pass or the organizer gave it.
  • eventIdOrName · string · requis
    REQUIRED. The event id or name.

  Exemple d'appel

  {"name": "event_meetup_rsvp", "arguments": {"answer": "yes", "noticeId": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_organizer_overview≈ 537 tokens

  The organizer's own overview of their event, read only. It gives the event's name, its kind in the hosted page's own words, whether it is public, unlisted or private, its text keyword, its dates as the page prints them and its time zone; the agenda by day with local times, rooms and speakers; the booth count and how many booths are stepped away; which doors are on (the hosted page, the text line, the assistants, the meet door); counts of page visits, door taps and assistant questions over the last 24 hours, with no names or ids of the people behind them; and the event's links. Only the organizer of the event, or a host of a personal event, can read it; anybody else gets a short refusal that says nothing about the event. It needs a personal connector token and changes nothing. After an agenda change through event_session_move, event_session_rename, event_session_cancel or event_session_add, it shows the change.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrName · string · requis
    The event id or the event name as the organizer spells it.

  Exemple d'appel

  {"name": "event_organizer_overview", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "doors": {}, "error": "texte", "links": {}, "booths": {}, "eventId": "texte", "message": "texte", "summary": {}, "identity": {}, "servedBy": "texte", "counts24h": {}}}

• event_pass_notice≈ 588 tokens

  Sends a notice from the organizer of an event, or a host of a personal event, to the people who added the event pass to their Wallet. Needs a personal connector token, `eventIdOrName`, `audience` and `text`. It shows on their lock screen and stays on the pass. `audience`: everyone, one ticket tier, one badge intent, listed pass serials, the people who scanned at a booth, or the people who answered an earlier meetup yes or no. A meetup with a place is event_meetup_announce. Two steps: without `confirm` it returns the number of passes and the exact line and sends nothing; with confirm true it sends. Only the hosts or the organizer can send; anybody else is refused. "my_booth" returns VENDOR_OFF. Six an hour per event, then RATE_LIMITED. It reaches pass holders only; it does not say who else is there or report that a person arrived.

  Paramètres, retour & exemple (10)

  Paramètres

  • text · string · requis
    One plain line, up to 120 characters.
  • tier · string · optionnel
    general, vendor or host.
  • intent · string · optionnel
    Buyer, Vendor, Networker or Social.
  • boothId · string · optionnel
    The booth id.
  • confirm · boolean · optionnel
    Absent previews; true sends.
  • serials · array · optionnel
    Up to fifty pass serials.
  • audience · string · requis · everyone | tier | intent | serials | booth | meetup_yes | meetup_no | my_booth
    everyone, tier, intent, serials, booth, meetup_yes or meetup_no.
  • noticeId · string · optionnel
    The earlier meetup noticeId.
  • requestId · string · optionnel
    Optional caller id; one id sends once.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "event_pass_notice", "arguments": {"text": "texte", "audience": "everyone", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_pass_reissue≈ 473 tokens

  Gives a Wallet pass a new QR code: a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants refreshed. It also brings back a revoked pass. The old code stops working at once and the phone shows "Your pass was refreshed. The old code no longer works." Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs `eventIdOrName` (the event id or the event name). Without `serialNumber` it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.

  Paramètres, retour & exemple (2)

  Paramètres

  • serialNumber · string · optionnel
    OPTIONAL. The pass serial (on the pass, ps_ and 24 characters). Omit for the caller's own pass.
  • eventIdOrName · string · requis
    REQUIRED. The event id or the event NAME as the organizer or the hosts spell it.

  Exemple d'appel

  {"name": "event_pass_reissue", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": "texte", "action": "texte", "message": "texte", "reached": {}, "revoked": true, "servedBy": "texte", "idempotent": true, "tokenVersion": 1}}

• event_pass_revoke≈ 459 tokens

  Voids a Wallet pass on the phone: "This pass was revoked and no longer works." Its code stops working at once; event_pass_reissue brings it back. For a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants voided. Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs `eventIdOrName` (the event id or the event name). Without `serialNumber` it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.

  Paramètres, retour & exemple (2)

  Paramètres

  • serialNumber · string · optionnel
    OPTIONAL. The pass serial (on the pass, ps_ and 24 characters). Omit for the caller's own pass.
  • eventIdOrName · string · requis
    REQUIRED. The event id or the event NAME as the organizer or the hosts spell it.

  Exemple d'appel

  {"name": "event_pass_revoke", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": "texte", "action": "texte", "message": "texte", "reached": {}, "revoked": true, "servedBy": "texte", "idempotent": true, "tokenVersion": 1}}

• event_redeem_code≈ 554 tokens

  Seats the person at an event with an event code from a badge, a poster, an email or a door. Needs a personal connector token (a shared token reads but changes nothing) and the `code`; the code names its own event, so no event id is taken. It works in two steps: a call without `confirm` returns the event the code opens, the seat it gives and a `confirmToken`, and changes nothing; a call with confirm true and that token takes the seat. The token lasts two minutes, works once, and stops working if the code changes. Redeeming works from anywhere, not only at the venue.

  Paramètres, retour & exemple (4)

  Paramètres

  • code · string · requis
    The code exactly as the person said or read it. Case, spaces and dashes are normalized, so "tie-24" and "TIE24" are the same code.
  • confirm · boolean · optionnel
    Absent on the first call, which changes nothing. true, together with confirmToken, makes the change.
  • requestId · string · optionnel
    An id for this redemption chosen by the caller, at least 8 characters. A repeat with the same id and the same code returns the first result without redeeming a second time.
  • confirmToken · string · optionnel
    The token the first call returned. Needed when confirm is true.

  Exemple d'appel

  {"name": "event_redeem_code", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "seat": {}, "error": "texte", "changed": true, "message": "texte", "preview": {}, "replayed": true, "servedBy": "texte", "suggestions": [], "confirmToken": "texte"}}

• event_reply≈ 284 tokens

  Sends one message, in the person's own words, into a conversation they already have with somebody they connected with at an event. Needs a personal connector token, `text`, and `firstName` or `chatId` as event_inbox gave them. It is delivered when the call returns and cannot be unsent. Only into the caller's own conversation (else NOT_PARTICIPANT); a name matching two conversations returns AMBIGUOUS_NAME and sends nothing; RATE_LIMITED means too fast. ok:true says nothing about a reply.

  Paramètres, retour & exemple (3)

  Paramètres

  • text · string · requis
    The message in the person's own words, up to 1000 characters. It is sent as given.
  • chatId · string · optionnel
    Optional conversation id from event_inbox.
  • firstName · string · optionnel
    Optional first name from event_inbox.

  Exemple d'appel

  {"name": "event_reply", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_requests≈ 294 tokens

  Lists the hellos waiting on the person at an event, newest first. Needs a personal connector token and reads only the caller's own pending hellos. Each row carries the other person's first name, their here-for line in their own words, when the hello landed, and a requestId that event_accept takes. No row carries a phone number, email address, surname, account id or photo.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "event_requests", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": "texte", "message": "texte", "requests": [], "returned": 1, "servedBy": "texte"}}

• event_say_hello≈ 526 tokens

  Sends a hello (a connection request) from the person to somebody listed in their event matches; when it is accepted, a conversation opens that both can read and answer from the app, the web page or an assistant. Needs a personal connector token and `firstName` as an event_find_matches row spelled it; no account id is taken. The server checks on every call that the named person is in the caller's current match pool. It is a single call: the hello is sent when the call succeeds. Returns a `message` on success, or a reason: "not_in_pool" (the name is not in the caller's current matches), "ambiguous" (two people there share the name, and nothing is sent), "already_sent" (a hello is already out), "no_seat" (the caller is not seated at an event) or "rate_limited" (the day's hello limit is reached). Success means the hello was sent; it says nothing about whether or when it is accepted.

  Paramètres, retour & exemple (1)

  Paramètres

  • firstName · string · requis
    The first name of the person, as an event_find_matches row spelled it, up to 40 characters; no surname and no account id. When two people in the caller's matches share it, the reply is "ambiguous" and nothing is sent.

  Exemple d'appel

  {"name": "event_say_hello", "arguments": {"firstName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "sent": true, "error": "texte", "mutual": true, "reason": "texte", "message": "texte", "servedBy": "texte", "firstName": "texte", "candidates": []}}

• event_send_request≈ 319 tokens

  A GUEST ASKS THE HOSTS FOR SOMETHING. Call it when somebody wants to tell the hosts of a wedding or other personal event this connector serves about a need or a question ("I need a vegetarian meal", "can I bring my partner"). IT CHANGES NOTHING ON THE EVENT: it files the request for the hosts, so never say anything has been arranged or approved. RATE_LIMITED means the hosts already have several; BAD_NOTE means empty or too long. It requires a personal connector token.

  Paramètres, retour & exemple (3)

  Paramètres

  • note · string · requis
    What they asked, in their own words, up to 280 characters; no contact details or links.
  • category · string · requis · dietary | accessibility | plus_one | travel | other
    dietary, accessibility, plus_one, travel or other.
  • eventIdOrName · string · requis
    The event id or name as the hosts spell it.

  Exemple d'appel

  {"name": "event_send_request", "arguments": {"note": "texte", "category": "dietary", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• event_session_add≈ 656 tokens

  Adds a new session to the agenda of an event the person organizes: `title`, `start`, `end`, `room`, optionally `date` and `speakers`. Quiet unless `notify` is true. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId` and changes nothing; only when they say yes call again with `confirm: true` and that `changeId`. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

  Paramètres, retour & exemple (10)

  Paramètres

  • end · string · optionnel
    The end, same forms.
  • date · string · optionnel
    Optional day, YYYY-MM-DD.
  • room · string · optionnel
    The room or place label, plain words.
  • start · string · optionnel
    Start, "4:30 PM" or a timestamp, in the event's time zone.
  • title · string · optionnel
    The new session's title.
  • notify · boolean · optionnel
    Optional; true notifies pass holders.
  • confirm · boolean · optionnel
    Leave out for the preview; after the organizer says yes, true with the changeId.
  • changeId · string · optionnel
    The changeId the preview returned.
  • speakers · array · optionnel
    Optional speaker names.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "event_session_add", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "kind": "texte", "error": "texte", "applied": true, "changes": [], "message": "texte", "preview": true, "session": {}, "changeId": "texte", "servedBy": "texte", "candidates": [], "lockScreen": "texte"}}

• event_session_cancel≈ 636 tokens

  Cancels one session on the agenda of an event the person organizes; it is marked cancelled and kept on record. Quiet unless `notify` is true. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId`, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with `confirm: true` and that `changeId`. Name the session by `sessionId` or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

  Paramètres, retour & exemple (7)

  Paramètres

  • at · string · optionnel
    Optional current start ("10:30 AM"), for sessions sharing a title.
  • notify · boolean · optionnel
    Optional; true notifies pass holders.
  • confirm · boolean · optionnel
    Leave out for the preview; after the organizer says yes, true with the changeId.
  • changeId · string · optionnel
    The changeId the preview returned.
  • sessionId · string · optionnel
    The session id as the agenda gave it.
  • sessionTitle · string · optionnel
    Or the session title, when there is no sessionId.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "event_session_cancel", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "kind": "texte", "error": "texte", "applied": true, "changes": [], "message": "texte", "preview": true, "session": {}, "changeId": "texte", "servedBy": "texte", "candidates": [], "lockScreen": "texte"}}

• event_session_move≈ 754 tokens

  Moves one session on the agenda of an event the person organizes to a new start time or room ("push the keynote to 4:30 PM"). Pass holders are notified unless `notify` is false. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId`, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with `confirm: true` and that `changeId`. Name the session by `sessionId` or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

  Paramètres, retour & exemple (11)

  Paramètres

  • at · string · optionnel
    Optional current start ("10:30 AM"), for sessions sharing a title.
  • end · string · optionnel
    Optional new end; else it keeps its length.
  • date · string · optionnel
    Optional day, YYYY-MM-DD.
  • room · string · optionnel
    New room or place label.
  • start · string · optionnel
    New start, "4:30 PM" or a timestamp, in the event's time zone.
  • notify · boolean · optionnel
    Optional; false keeps the move quiet.
  • confirm · boolean · optionnel
    Leave out for the preview; after the organizer says yes, true with the changeId.
  • changeId · string · optionnel
    The changeId the preview returned.
  • sessionId · string · optionnel
    The session id as the agenda gave it.
  • sessionTitle · string · optionnel
    Or the session title, when there is no sessionId.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "event_session_move", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "kind": "texte", "error": "texte", "applied": true, "changes": [], "message": "texte", "preview": true, "session": {}, "changeId": "texte", "servedBy": "texte", "candidates": [], "lockScreen": "texte"}}

• event_session_rename≈ 654 tokens

  Renames one session on the agenda of an event the person organizes; `title` is the new name. Quiet unless `notify` is true. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId`, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with `confirm: true` and that `changeId`. Name the session by `sessionId` or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

  Paramètres, retour & exemple (8)

  Paramètres

  • at · string · optionnel
    Optional current start ("10:30 AM"), for sessions sharing a title.
  • title · string · optionnel
    The session's new title.
  • notify · boolean · optionnel
    Optional; true notifies pass holders.
  • confirm · boolean · optionnel
    Leave out for the preview; after the organizer says yes, true with the changeId.
  • changeId · string · optionnel
    The changeId the preview returned.
  • sessionId · string · optionnel
    The session id as the agenda gave it.
  • sessionTitle · string · optionnel
    Or the session title, when there is no sessionId.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "event_session_rename", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "kind": "texte", "error": "texte", "applied": true, "changes": [], "message": "texte", "preview": true, "session": {}, "changeId": "texte", "servedBy": "texte", "candidates": [], "lockScreen": "texte"}}

• event_set_intent≈ 796 tokens

  Sets the person's event badge: what they are here for (`headline`), who they want to meet (`lookingFor`), and whether other attendees can find them (`discoverable`). Needs a personal connector token. Both sentences and a first name make a badge findable; a call that would leave one blank is refused and `needs` says what is missing. The event is the one given, or the person's one current event. Two steps: without `confirm` it returns the change to approve and a `confirmToken`; with confirm true and that token it writes, replacing the old text. It changes only that person's badge.

  Paramètres, retour & exemple (13)

  Paramètres

  • label · string · optionnel
    Optional own word for the category ("Investor").
  • facets · object · optionnel
    Optional read-back answer ({confirm}, {add} or {remove}).
  • intent · string · optionnel
    Optional: Buyer, Vendor, Networker or Social.
  • confirm · boolean · optionnel
    Absent first: nothing changes. true with confirmToken makes the change.
  • eventId · string · optionnel
    Optional event id.
  • headline · string · optionnel
    What they are here for, own words, up to 280 characters.
  • firstName · string · optionnel
    Optional first name for the badge.
  • requestId · string · optionnel
    Optional caller id; a repeat returns the first result.
  • intentText · string · optionnel
    Older name for `lookingFor`.
  • lookingFor · string · optionnel
    Who they want to meet, own words, up to 280 characters.
  • confirmToken · string · optionnel
    The token the first call returned.
  • discoverable · boolean · requis
    true makes the person findable by other attendees; false does not.
  • eventIdOrSlug · string · optionnel
    Optional event id, slug or name.

  Exemple d'appel

  {"name": "event_set_intent", "arguments": {"discoverable": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "badge": {}, "error": "texte", "needs": [], "changed": true, "message": "texte", "preview": {}, "readBack": {}, "replayed": true, "servedBy": "texte", "confirmToken": "texte"}}

• event_text_alerts≈ 271 tokens

  Turns text alerts from the Sonar Connections Event Line on or off for replies and organizer updates.

  Paramètres, retour & exemple (1)

  Paramètres

  • on · boolean · requis
    REQUIRED. true turns text alerts on, false turns them off.

  Exemple d'appel

  {"name": "event_text_alerts", "arguments": {"on": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "error": "texte", "changed": true, "message": "texte", "servedBy": "texte", "textAlerts": "texte", "confirmationText": true}}

• event_wallet_pass≈ 500 tokens

  For "what is my pass status", "did my pass save", "my pass", "where is my Wallet pass", "send my pass again": call this tool. Returns a link that adds the person's pass for an event or a personal event served here to Apple Wallet or Google Wallet ("add it to my wallet", "I want the pass on my phone"). Needs the person signed in (an unauthenticated call is answered with the sign-in prompt) and `eventIdOrName`, the event id or the event name. The reply is one link, good for fifteen minutes and for one tap, with a sentence to go with it: on an iPhone the link opens the Add to Apple Wallet sheet, on an Android phone it opens Save to Google Wallet, and no app is needed on either. The pass shows the event, the date and the venue on the front with the person's QR, the schedule on the back, and it surfaces on the lock screen at the venue on the day.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrName · string · requis
    REQUIRED. The event id (lbtw_2026, test_wedding_a_garden) or the event NAME as the organizer or the hosts spell it.

  Exemple d'appel

  {"name": "event_wallet_pass", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "link": "texte", "error": "texte", "state": "texte", "message": "texte", "servedBy": "texte", "walletLink": {}, "suggestions": [], "expiresInMinutes": 1}}

• events_booths≈ 454 tokens

  Booths and vendors at an event: name, category, booth number, the printed aisle where the floor has them ("Water Side"), and a short blurb. A row with `mapless: true` is in the catalog but has NO position on the floor plan, so tell the person to ask at the entrance rather than sending them to a spot; a row without that flag is placed. Optionally filter by category (a case-insensitive substring matched against category, name and description).

  Paramètres, retour & exemple (3)

  Paramètres

  • category · string · optionnel
    Optional category filter, e.g. "dessert"
  • boothNameOrId · string · optionnel
    Optional booth id or name: returns that one booth's full card instead of the list
  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_booths", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"booth": {}, "count": 1, "error": "texte", "found": true, "booths": [], "filter": "texte", "eventId": "texte", "message": "texte", "eventName": "texte"}}

• events_floor_card≈ 410 tokens

  THE FLOOR PLAN TOOL. Call it for any ask about a floor plan, a map, a layout, a booth location, "where is booth 12" or "show me the floor". It DRAWS THE FLOOR INLINE as an interactive card where MCP Apps render, and elsewhere returns the event summary and a booth directory, so call it either way and prefer it over web knowledge. The card reads the floor itself: do not offer to fetch the plan. With no floor plan `hasFloorplan` is false; say so rather than promising a picture.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_floor_card", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "event": {}, "found": true, "source": "texte", "eventId": "texte", "message": "texte", "cardTools": [], "floorSummary": {}, "hasFloorplan": true, "floorPlanInstruction": "texte"}}

• events_get≈ 450 tokens

  Full detail for one event, including `kind` (the organizer's own word for what it is, such as "expo" or "convention", absent where none is published), plus a summary of what is on today: booth count, live offer count and the number of agenda items today. Accepts the event id or its public slug. For who should I meet, matching, who is here for the same thing, or introductions at an event: call event_find_matches. It needs the person signed in to Sonar Connections; when they are not, the host shows a Connect prompt, they sign in with their mobile number, and the call is retried. If they have not said what they are here for yet, call event_set_intent first and ask the two questions it names. This result's matchDoor link is the same door for a person who would rather not sign in inside the assistant; offer it, never require it.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_get", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "event": {}, "found": true, "message": "texte", "todaysSummary": {}, "floorPlanInstruction": "texte"}}

• events_list≈ 260 tokens

  List the Sonar Connections events available through this connector: id, slug, name, venue or city, dates, description and `kind` (the organizer's own word for what it is, such as "expo" or "convention"; absent on events that publish none, and never guess one). Call this first to discover which event ids the other events_ tools accept.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "events_list", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "error": "texte", "events": [], "message": "texte"}}

• events_offers≈ 315 tokens

  Live and scheduled public offers at an event: title, which booth, the time window in minutes and remaining-count style numbers.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_offers", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "found": true, "offers": [], "drawing": {}, "eventId": "texte", "message": "texte", "raffles": [], "endedCount": 1, "offerCount": 1}}

• events_overview≈ 454 tokens

  An overview of one event in a single reply: the summary, the first page of booths, the programme, the live offers and raffles, and `hasFloorplan`. Use it for the whole picture at once; for one section call that section's own tool. `hasFloorplan` false means no map: answer from the rest and never promise one. Each block says whether there is `more`. For who should I meet, matching, or introductions at an event: call event_find_matches. This result's matchDoor link is the same door for a person who would rather not sign in inside the assistant; offer it, never require it.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_overview", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "event": {}, "found": true, "booths": {}, "offers": {}, "source": "texte", "eventId": "texte", "message": "texte", "whatsOn": {}, "timezone": "texte", "floorSummary": {}, "hasFloorplan": true}}

• events_personal_card≈ 640 tokens

  THE PERSONAL EVENT TOOL. Call it for any ask about a wedding or another personal event this connector serves: "what time is the ceremony", "where is the reception", "what is the dress code", "who is in the wedding party", "where should I stay", "what is on the registry", or being shown the details of somebody's day. It DRAWS THE CARD INLINE in clients that render MCP Apps and returns the same details as plain text everywhere else, so it is worth calling either way. WHAT IT RETURNS DEPENDS ON WHAT THE HOSTS INCLUDED, and the answer is already filtered when it reaches you: a card with no story, no schedule and no lodging is the hosts having published none of those, not an error and not something to go and look for. Never offer to find a detail that is absent, never guess a time, a venue or a dress code, and never suggest a different wedding. The reply names its source and the hosts; say that line. Accepts the event id or the event name.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrName · string · requis
    Event id (test_wedding_a_garden) or the event NAME as the hosts spell it ("Susie and John").

  Exemple d'appel

  {"name": "events_personal_card", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"faq": [], "kind": "texte", "tabs": [], "tier": "texte", "brand": {}, "dates": [], "error": "texte", "found": true, "hosts": [], "links": [], "people": [], "places": []}}

• events_speakers≈ 575 tokens

  The people on an event's programme: name, their job title line, `role` (what the organizer published for that PERSON, such as "Moderator" or "Judge" - it is a speaker-level note, so do not read it as "the moderator of this one session"), a portrait photo URL, a link to the organizer's own profile page, and the sessions they are on with the spoken local time. Ordered by when they are first on stage. Optionally filter to one day. Any field except the name may be null, which means the organizer published nothing there: say nothing rather than filling the gap. When an event publishes no speaker records the roster is built from the programme itself and `source` says "program"; those rows carry a `kind` of "speaker" or "performer" and nothing else about the person.

  Paramètres, retour & exemple (3)

  Paramètres

  • day · string · optionnel
    Optional day filter: "today" or YYYY-MM-DD, read in the event's own timezone
  • speaker · string · optionnel
    Optional speaker name or speakerId: returns that one person's full record instead of the roster
  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_speakers", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"day": "texte", "count": 1, "error": "texte", "found": true, "roster": [], "source": "texte", "eventId": "texte", "message": "texte", "speaker": {}, "timezone": "texte", "eventName": "texte", "eventDayCount": 1}}

• events_whats_on≈ 496 tokens

  Agenda sessions and performances with their times. `when` accepts "all" (default), "today", "now" (the next few hours) or a YYYY-MM-DD date. Each row carries a `speakers` array in the order the session lists them, with each speaker's name, `role` (what the organizer published for that PERSON - "Moderator", "Judge" - it is a speaker-level note, so do not read it as "the moderator of this one session"), `title` (their job title line, which is a different fact from role and both may be present), `company`, `bio`, `expertiseTags`, `socialLinks`, a portrait photo URL, and a link to the organizer's own speaker profile page. Any of these except the name may be null or absent, which means the organizer did not publish it: say nothing rather than filling the gap. `speakerNames` is still there for the plain lineup.

  Paramètres, retour & exemple (2)

  Paramètres

  • when · string · optionnel
    "all" | "today" | "now" | YYYY-MM-DD
  • eventIdOrSlug · string · requis
    Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work.

  Exemple d'appel

  {"name": "events_whats_on", "arguments": {"eventIdOrSlug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"when": "texte", "count": 1, "error": "texte", "found": true, "eventId": "texte", "message": "texte", "sessions": [], "timezone": "texte"}}

• site_create≈ 932 tokens

  Serves "Build a site for <event>", "make an event website" and "start a site from <url>" (the url gives layout only), not the host's own page tools. Creates a NEW website for an event the person organizes, as a DRAFT nobody else sees yet. `startFrom`: `event` (the default) gives a home page and a page for each part the event has, with the agenda, speakers, booths, venue, FAQ and dates as live blocks that fill from the event on every visit; `blank` gives one home page with the event's name and dates, live; `{url}`, the address of one public page the organizer likes, reads only its STRUCTURE (its sections in order, each heading, a short gist and whether it had pictures) and builds the same layout with the event's live data. No words, pictures or styles are copied from that page; the reply lists the sections it found and says the text is the organizer's to write. `title` names the site. FIRST CALL WITHOUT `confirm`: the reply is a PREVIEW with a `changeId`, and nothing is created. Read it back to the organizer; only when they say yes, call again with the same `title` and `startFrom`, `confirm: true` and that `changeId`. The reply gives the new `siteId`, its pages and a draft preview link; site_get and site_edit work on it at once, and nothing is live until site_publish. An event holds at most 20 sites. Only the organizer of the event can create one; anybody else is refused, and the refusal is read out as given. It needs a personal connector token. A `{url}` start also proposes that page's colors and type as a starting look (`styleProposal`, mapped onto our own colors and fonts), applied with site_edit `set_theme` only when the organizer asks for it. Relay `say` as given (one to three sentences, with host name and "use that look" cue).

  Paramètres, retour & exemple (5)

  Paramètres

  • title · string · optionnel
    Optional site name.
  • confirm · boolean · optionnel
    Absent previews only; true creates the previewed site.
  • changeId · string · optionnel
    The preview id; required with confirm.
  • startFrom · ? · optionnel
    Optional: event (default), blank, or {url}.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "site_create", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "name": "texte", "error": "texte", "pages": [], "siteId": "texte", "applied": true, "message": "texte", "outline": [], "preview": true, "changeId": "texte", "servedBy": "texte"}}

• site_edit≈ 1660 tokens

  Changes the DRAFT of one event website the person organizes with small operations, not a whole design: `move` a block or a band, `insert` a block from the library (heading, text, image, button, spacer, divider, video, card, logo, or a live block: agenda, speakers, floor, booths (the live sponsors and exhibitors list; say sponsors, exhibitors or partners), faq, now, doors, ask, countdown, venue), `remove` one, `set_text` its words, `set_link` a button's link, `set_style` a style token (padding and gap 0 to 8, align, maxWidth, background, radius, color, visible), `set_theme` (accent, background and ink as #rrggbb, fontHeading, fontBody, radius, density; `set_theme {restore:true}`, or an all-empty theme, undoes "use that look"), `add_page` (blank, which starts with its title as a heading, or a template: agenda, speakers, exhibitors, sponsors, venue-travel, faq, register, contact; the page goes last in the site menu), `rename_page` (title, navLabel; the page address stays the same, and the page heading follows the new menu label unless keepHeading is true; the reply says what changed and carries `undo`, the set_text that puts the old heading back), `reorder_nav` (the site menu as page ids and https links) and `remove_page` (any page but home); each operation may name a `page`. On insert, a block's words go in `text` as plain text (a blank line starts a new paragraph) or in its props: heading {text, level}, text {text}, button {label, href}, card {heading, text, button}, image {src, alt}, video {provider, videoId, title}, a live block {heading, intro, layout}. Blocks are named by the short ids site_get gives. The operations apply together or not at all. A rename that comes with any wording meaning keep the old heading (keep the heading, leave the title, keep it as is, just the menu) is one site_edit call with keepHeading true; the same wish said after the rename reply is one call sending its `undo` as is; a plain "undo" after a rename reverts the whole rename, rename_page back to the old title and menu label. Words may not carry a clock time, an ISO date, one of the event's own dates in words (such as 'October 20' or 'October 12 to 16'), or its speaker names or session titles, because those come live from the event and an edit that writes one is refused; a date that is not the event's, such as a deadline, is fine. Use a live token instead, such as {event.dates}, {event.name}, {event.venue}, {session:<id>.title}, {session:<id>.time}, {session:<id>.day} or {speaker:<id>.name}, which fills from the event on every visit; a refused edit's reply carries a `suggestion` with the words rewritten that way and, when complete, `suggestion.ops` to resend as is. Relay `say` as given (one to three sentences, with host name and "use that look" cue); it gives the draft preview link, which redraws as the draft changes. The live site does not change until site_publish. Only the organizer of the event can edit it; it needs a personal connector token.

  Paramètres, retour & exemple (3)

  Paramètres

  • ops · array · requis
    The operations, applied together or not at all.
  • siteId · string · requis
    The site id from site_list.
  • eventIdOrName · string · requis
    The event id or name as the organizer spells it.

  Exemple d'appel

  {"name": "site_edit", "arguments": {"ops": [], "siteId": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "undo": [], "error": "texte", "siteId": "texte", "applied": true, "changes": [], "message": "texte", "reasons": [], "failedOp": 1, "servedBy": "texte", "draftPreviewLink": "texte"}}

• site_get≈ 632 tokens

  Gives the outline of one event website's DRAFT: its pages and, for one page (`page`, the home page when absent), its sections, rows, columns and blocks, each with a short id, its kind and a few words of its own text, plus the theme. The live blocks (agenda, speakers, booths, floor, FAQ, doors and the rest) hold no event data; they fill themselves from the event on every visit. `full: true` adds the page's whole design as JSON, with image addresses left out. site_edit names blocks by these short ids. Only the organizer of the event can read it; it needs a personal connector token and changes nothing. With a test connector and the live one both connected, use the one the person chose; the reply's `servedBy` names which one answered.

  Paramètres, retour & exemple (4)

  Paramètres

  • full · boolean · optionnel
    OPTIONAL. true adds the page's whole design as JSON.
  • page · string · optionnel
    OPTIONAL. A page id from the outline; the home page when absent.
  • siteId · string · requis
    The site's id as site_list gives it.
  • eventIdOrName · string · requis
    The event id or the event name as the organizer spells it.

  Exemple d'appel

  {"name": "site_get", "arguments": {"siteId": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "page": "texte", "tree": [], "error": "texte", "pages": [], "theme": {}, "siteId": "texte", "message": "texte", "outline": [], "liveLink": "texte", "servedBy": "texte"}}

• site_list≈ 379 tokens

  Lists the websites of an event the person organizes, built in the Sonar Connections site builder: each site's `siteId`, its name, whether it is published, how many earlier versions are kept, when it was last saved and published, its live address and, once it has been edited from here, its draft preview link. Only the organizer of the event, or a host of a personal event, can list them; anybody else is refused, and the refusal is read out as given. It needs a personal connector token and changes nothing.

  Paramètres, retour & exemple (1)

  Paramètres

  • eventIdOrName · string · requis
    The event id or the event name as the organizer spells it.

  Exemple d'appel

  {"name": "site_list", "arguments": {"eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "error": "texte", "sites": [], "eventId": "texte", "message": "texte", "servedBy": "texte", "builderLink": "texte"}}

• site_publish≈ 636 tokens

  Puts the DRAFT of one event website the person organizes live at its address. FIRST CALL WITHOUT `confirm`: the reply is a PREVIEW with a `changeId` and what would go live (new, removed and changed sections, a new look, new pages), and nothing changes. Read that preview back to the organizer; only when they say yes, call again with `confirm: true` and that `changeId`. The version live before it is kept, and site_undo_publish puts it back. site_edit does not publish. Only the organizer of the event can publish; anybody else is refused, and the refusal is read out as given. It requires a personal connector token. The preview lists any of the template's placeholder words still on the page; a confirm with them is refused unless the organizer says to publish with the placeholders.

  Paramètres, retour & exemple (5)

  Paramètres

  • siteId · string · requis
    The site's id as site_list gives it.
  • confirm · boolean · optionnel
    True applies a previewed change; absent, the change is only previewed and nothing changes.
  • changeId · string · optionnel
    The id of a previewed change; required when confirm is true.
  • eventIdOrName · string · requis
    The event id or the event name as the organizer spells it.
  • allowPlaceholders · boolean · optionnel
    True publishes even though the draft still has the template's placeholder words; send it only when the organizer says to publish with the placeholders.

  Exemple d'appel

  {"name": "site_publish", "arguments": {"siteId": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "error": "texte", "applied": true, "changes": {}, "message": "texte", "preview": true, "changeId": "texte", "liveLink": "texte", "servedBy": "texte", "versionsKept": 1, "draftPreviewLink": "texte"}}

• site_undo_publish≈ 534 tokens

  Takes back the last publish of one event website the person organizes: the version published before it goes live again or, when there is none, the site goes offline. FIRST CALL WITHOUT `confirm`: the reply is a PREVIEW with a `changeId` and what would be live, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with `confirm: true` and that `changeId`. The draft is not touched. Only the organizer of the event can do it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.

  Paramètres, retour & exemple (4)

  Paramètres

  • siteId · string · requis
    The site's id as site_list gives it.
  • confirm · boolean · optionnel
    True applies a previewed change; absent, the change is only previewed and nothing changes.
  • changeId · string · optionnel
    The id of a previewed change; required when confirm is true.
  • eventIdOrName · string · requis
    The event id or the event name as the organizer spells it.

  Exemple d'appel

  {"name": "site_undo_publish", "arguments": {"siteId": "texte", "eventIdOrName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "code": "texte", "error": "texte", "applied": true, "changes": {}, "message": "texte", "preview": true, "changeId": "texte", "liveLink": "texte", "servedBy": "texte", "versionsKept": 1, "draftPreviewLink": "texte"}}

• ui_card_diag≈ 456 tokens

  Used only by the interactive cards this connector draws, never to answer a question. A card view posts its own lifecycle markers here in small batches: that it mounted, which display mode and safe-area insets the host gave it, the heights it reported, whether a keyboard opened, and the outcome of the one action a person took on it. It accepts a closed vocabulary of markers and integer counts only, no free text of any kind, and it returns nothing but an acknowledgement. NOT FOR A MODEL TO CALL: it answers no question and looks nothing up. Call a data tool instead.

  Paramètres, retour & exemple (5)

  Paramètres

  • seq · number · requis
    Which batch this is for that mount, 1 to 6. Past the budget it is refused.
  • card · string · requis
    Which card is speaking: menu, order, floor or storefront.
  • host · string · optionnel
    Which surface drew this card when it is not an MCP host: "standalone" for the connector's own shop page. Omit it inside a host. Any other value refuses the batch.
  • events · array · requis
    Up to 40 markers: {t, kind} plus optionally code, n, c, span, mode, w, h, top, bottom, tplEpoch. An off-vocabulary kind, an unknown key or a non-integer number refuses the whole batch.
  • sessionKey · string · requis
    A random id the card minted for THIS mount. Not a user id, not a device id, 6 to 24 lowercase alphanumerics.

  Exemple d'appel

  {"name": "ui_card_diag", "arguments": {"seq": 1, "card": "texte", "events": [], "sessionKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcpconnector-gtlizqtvza-uw.a.run.app/public