Could Have Been Email

live EntertainmentProductivity

Analyzes meeting transcripts to evaluate whether the meeting could have been an email, with filler-word counts and a draft replacement email.

1 tools
0ms auth
free tier 50 calls/day

Tools

could_have_been_email_analyze

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.

No parameters required.

▶ 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":{}}}'

Use with the SDK

Install @pipeworx/sdk to call tools from any TypeScript/Node project.

TypeScript 
import { Pipeworx } from '@pipeworx/sdk';
const px = new Pipeworx();
const result = await px.call("could_have_been_email_analyze", {});
ask_pipeworx 
// Or ask in plain English:
const answer = await px.ask("analyzes meeting transcripts to evaluate whether the meeting could have been an email, with filler-word counts and a draft replacement email");