Skip to main content
Glama

Tenda

Choose where Tenda's alerts go

choose_alerts
DestructiveIdempotent

Use this when the user wants to change which Slack and Teams channels get Tenda's alerts, or asks where they go: "stop the morning summary in Slack". Change only what the user asked for; with neither send nor stop it changes nothing and says where alerts go now. Owners and admins can change alerts. Needs a Tenda account and workspace. Not for connecting a channel (Tenda dashboard, Settings, Connections) or for email alerts (use watch_tenders). Example: {"app":"slack","stop":["morning_summary"]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNo"slack" or "teams" for that app's channels. Leave out app and channel for every channel.
onlyNotrue when what's sent here should go only here: every other channel stops getting it. An app or channel the user didn't mention otherwise keeps its alerts.
sendNoAlerts to turn on in those channels: "new_tenders" (new tenders that fit the company), "changes" (changes to tenders in the pipeline), "morning_summary" (the weekday morning summary), "bid_work" (bid work nobody has yet), or "all".
stopNoAlerts to turn off in those channels: "new_tenders" (new tenders that fit the company), "changes" (changes to tenders in the pipeline), "morning_summary" (the weekday morning summary), "bid_work" (bid work nobody has yet), or "all". A channel with no alerts stays connected, so the team can still ask Tenda there.
channelNoOne channel, by its name: e.g. "bids" or "#bids" in Slack, or "General" in Teams.
workspaceNoThe Tenda workspace to use, by name, when the user is in more than one, e.g. "Northbridge Services".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNo
summaryYes
channelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources