EventMatch

View saved version →

---
name: event-workspace
description: Read authorized EventMatch Events, event People profiles and saved prospecting plans. Does not start Event Mode, research, processing or outreach.
---

# EventMatch public workspace

Use only the connected public EventMatch MCP tools available in the current host.
For "now" or "soon", resolve `get_current_event_context` first; overlapping events
require a selection. Otherwise open `render_event_workspace` to search Events.
Select an exact event ID before reading People or a plan.

- `get_event_overview`: stored original description, existing AI brief and linked
  organizers. Host names without a Person link remain text, not inferred identity.
- `list_event_people`: stable Person IDs at this authorized event; reset cursor
  when the search changes. Each page is at most 20.
- `get_event_person_profile`: canonical professional profile, saved sources,
  labeled hypotheses, unknowns and optional existing assessment. A missing score
  does not mean that the Person is unavailable.
- `get_event_workspace_plan`: existing meeting order and questions. Use its
  analysis ID when opening a linked Person so the context remains consistent.

If these 1.1 tools are not yet available, use the existing 1.0 read-only tools;
do not claim that the new UI is installed or approved. If the UI bridge is absent,
summarize the tool result in text. Never claim stored research is a live lookup.

Reading never queues generation or synchronization. Missing data stays missing.
Drafts are unsent and require user review. The public app has no access to My picks,
personal Prepare/follow-up notes, encounters, camera, QR, media, Omi transcripts,
biometrics, contacts hidden by the provider, identity review or browser controls.
Do not invoke personal/admin tools to satisfy a public request. Sending messages,
registration and processing are unavailable even if the user asks for them.