Use Domino from an assistant
MCP tool names and Capability API operation names are shared. For the API, send {"version":"1.0","input":{...}} to POST /api/v2/capabilities/{name}. MCP writes take idempotency_key. API writes take an Idempotency-Key header. Use the reference and version returned by the preceding action. Operation reference
| User request | Operations and evidence |
|---|---|
| What needs my attention? | Use status for current invitations, upcoming plans and coordination. Use topic=history for historical unfinished work. |
| Find this restaurant, or suggest a date night | find retrieves direct matches. recommend ranks possibilities. Present the returned outing text and web link. For a brief request one option. Revise the same displayed outing by reference and preserve the other choices. |
| What did I Like for Andrew and Victor together? | Use list with kind=likes, both names in filters.people_names, and filters.intention_match=exact. For reciprocal interest, use kind=mutual_interest. Incoming interest has its own kind. |
| Save this reel for a friend | Use save_ideas. Read the same capture through completion, then use its saved identity in planning. Capture and recovery |
| Organize ideas | Use edit_view for a live filter over Likes. edit_selection edits an existing hand-picked selection using its revision. Use list or get to reopen each kind. |
| Find time together | Use free_time. State which calendars contributed, unknown coverage and the time zone. Venue opening hours and booking availability are separate facts. |
| Keep research for later | record_research retains the selected identities, constraints, sources and uncertainty. Use the returned selection for saving or private planning. |
| Invite someone | For a displayed outing, a go-ahead opens prepare_plan(task=outing). Present its confirmation text as written. A later yes approves that exact review. Use edit_draft when a separate draft is needed. For an identified plan, prepare_plan can prepare the review directly. Use action=send_invites for named people, including manually delivered invitations. Review who, what, when, where and delivery. A later approval authorizes confirm for that exact reference. |
| Share Likes or change a friendship | Use prepare_share for the selected Likes or review_connection for a friendship change. A new invitation requires explicit people_handles; [] intentionally creates an unnamed join link with no retained Likes. Present the returned audience, included ideas, visibility and effects before confirmation, even with the public preview off. Deliver a returned manual link separately. |
| Respond to an invite | Open the incoming invitation and use rsvp for the requested response. Inspect the new status. Use the web link for recipient-only steps the connection cannot perform. |
| Update an existing plan | Open its roster or logistics using get. Use prepare_plan for a time, roster or cancellation review. edit_checklist identifies which changes require a guest-visible review. |
When a result offers a choice, link to the exact web view supplied. For more records use the collection cursor. For a large detail use its returned detail field and continuation. When completion is uncertain, inspect the receipt before repeating a write. Use get with kind=input_help, the operation name, choice and optional field to look up variant-specific requirements.