call id - 56f62483-bfcf-4348-b93c-97b16b63e89b

@Kings_big💫 what's the update

Any updates would be helpful

cmon guys, have to use Retell ai now

lol

call_id: 56f62483-bfcf-4348-b93c-97b16b63e89b

logs

🔵 15:08:02:679 [user ERROR] Tool

mcp:Slack-Operations

failed (reason: mcp server https://mcp.zapier.com/api/mcp/s/NmxjOQ==/mcp rejected request) 🔵 15:08:03:420 Conversation Buffer Appending Tool Result. Emitting "conversation-update"... [ { "role": "tool_call_result", "time": 1749568083419, "secondsFromStart": 43.238, "name": "Slack-Operations", "result": "{\"error\": \"Failed to connect to MCP server\"}", "toolCallId": "call_kyqmtJLlwM9qEjrUBUC56yrm" } ] 🔵 15:08:02:483 Converted Requested Tools Calls To Internal Format. [ { "type": "mcp", "server": { "url": "https://mcp.zapier.com/api/mcp/s/NmU3xxxxdjOQ==/mcp", "headers": { "X-Call-Id": "56fxxxxx63e89b" } }, "messages": [], "function": { "name": "Slack-Operations", "description": "Performs any slack opperation", "parameters": {"type": "object", "properties": {}, "required": []} }, "toolCall": { "id": "call_kyqmxxxx56yrm", "type": "function", "function": {"name": "Slack-Operations", "arguments": {}} } } ] As you can see from the call logs, your MCP server rejected the requests. It's not Vapi. Please check your mcp logs to understand why and what actions you can take to accept the REQUEST. I've attached the request we sent as well. cc: @User @User @User @User

@n0tmadI reviewed the shared chat ID logs, but I couldn't make any definitive conclusions. Please provide a working call ID or chat ID example to compare them. Also, if you have more similars call IDs or chat IDs for your case, that would be helpful. cc: @Kings_big💫 @Joseph @mukul

i am using n8n and it uses SSE

just made this call

please check

any updates guys?

?

Hey guys any fixes ? @User

Any updates?

Its been 3 days already

I will keep on pinging till my error is solved

@Kings_big💫 whats the update?

did you check?

why the support system is so slow?

@n0tmad I've completed a thorough investigation of the MCP tool failure you experienced during your calendar booking call. Here's what we found and how you can resolved it: Your assistant was throwing MCP error -32603: Tool not found when people tried to book appointments. The assistant kept calling mcp_tool instead of the actual calendar functions. What You've Done to Resolve This - Updated the system prompts to reference specific calendar tools rather than the generic MCP tool -

current

Trigger mcp_tool for all tasks related to calendar, meetings & bookings

example

[Identity]
You are a professional calendar assistant that can book, modify, and manage appointments.

[Response Guidelines]
- Always confirm appointment details before booking
- Default to 1-hour appointments unless specified otherwise
- Present times in user-friendly format (e.g., "8:30 AM tomorrow")
- Use ISO format for actual tool calls

[Task & Tools]
For appointment requests like "Can you book an appointment for 8:30 tomorrow?":
1. Use n8n-Create_event with:
   - Start: Convert user time to ISO format
   - End: Add 1 hour to start time (unless specified)
2. Confirm successful booking with user

For modifications: Use n8n-Get_event first, then n8n-Update_event
For cancellations: Use n8n-Get_event first, then n8n-Delete_event

Try your calendar booking flow again, and Let me know how the testing goes! cc: @Kings_big💫