could_have_been_email_analyze
ActiveTool of Could Have Been Email
declared in 0.1.0
Check if a meeting transcript could have been an email instead. Returns filler word count, decisions made, action items, and a suggested email that would've replaced the meeting.
Parameters schema
{
"type": "object",
"examples": [
{
"duration": 15,
"recurring": true,
"transcript": "Team standup: John reported completion of API integration. Sarah discussed Q4 roadmap priorities. Mike raised concern about database performance. Action: John to share API docs by Friday.",
"attendee_count": 5
},
{
"duration": 45,
"transcript": "All-hands meeting covering company performance, new benefits rollout, and office reopening policy. HR presented three policy options. Finance reviewed quarterly results. Q&A about remote work flexibility.",
"attendee_count": 32
}
],
"required": [
"transcript"
],
"properties": {
"duration": {
"type": "number",
"description": "Meeting duration in minutes"
},
"recurring": {
"type": "boolean",
"description": "Is this a recurring meeting"
},
"transcript": {
"type": "string",
"description": "Meeting transcript or summary"
},
"attendee_count": {
"type": "number",
"description": "Number of attendees"
}
}
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
Could Have Been Email
https://github.com/pipeworx-io/mcp-could-have-been-email
1/7 registries