Could Have Been Email

live Humor

Analyze a meeting transcript to determine if it could have been an email

1 tools
0ms auth
free tier 50 calls/day

Tools

could_have_been_email_analyze required: transcript

Analyze a meeting transcript to determine if it could have been an email. Counts filler, decisions, action items, and generates the email that should have been sent instead.

Parameters
Name Type Description
transcript req string Meeting transcript or summary
duration opt number Meeting duration in minutes
attendee_count opt number Number of attendees
recurring opt boolean Is this a recurring meeting
▶ Try it

Test with curl

The gateway speaks JSON-RPC 2.0 over HTTP POST. You can test any pack directly from the terminal.

List available tools
bash 
curl -X POST https://gateway.pipeworx.io/could-have-been-email/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Call a tool
bash 
curl -X POST https://gateway.pipeworx.io/could-have-been-email/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"could_have_been_email_analyze","arguments":{"transcript": "example"}}}'