How the WHOLE workspace is doing, its Dashboard: every table at once. For the window asked for (days ending today, or a from..to range) and the one before it: the flow of its people and of its accounts over eight steps (added, enrolled in a workflow, reached, engaged, replied, positive, meeting, won), each counted once on the day they first got there, so a reply rate is replied over reached and a change is shown against before; where everyone stands today at each step (here: still in progress; left: gone to a nurture, negative or disqualified stage); the same window counts per table (which table brings replies or meetings); the window's people by source kind and the ones reached per channel; the money open today and won in the window; and the people by stage category at the end of each day. Narrow it with playtable_sids (those tables' people and accounts) or sender_profile_sids (the people those sender profiles first touched or enrolled). Use for "how is outreach going", "is the pipeline growing", "which table works best", "how many people did we reach this week", "how did Julia's outreach go this month". One table's own flow, all time: get_playtable_performance.

Contract:

• MCP tool get_workspace_performance, registry package mcp.playtables/playtables, mount playtables.tables.
• Operation action, response envelope action.
• Flags: read only.