Skip to main content
Glama

delimit_notify

Send notifications via webhook, Slack, or email when owner action is required. Auto-triggered for outreach replies, deployment decisions, and approval alerts.

Instructions

Send a notification (webhook / Slack / email) (Pro).

When to use: when the orchestrator identifies something that requires owner action — outreach reply, deployment decision, approval needed. Auto-trigger: call immediately, never ask. When NOT to use: for SIEM-class structured streaming (use delimit_siem) or multi-routing config (delimit_notify_routing).

Sibling contrast: delimit_notify_routing configures rules; delimit_notify_inbox reads inbound; this sends one outbound.

Side effects: gated by require_premium. Sends a network message via webhook (JSON POST), Slack webhook, or email (SMTP). The founder reviews and replies via email — that reply is consumed by delimit_notify_inbox / delimit_inbox_daemon.

IMPORTANT - AUTO-TRIGGER RULE: When the AI identifies something requiring owner action (outreach reply, deployment decision, approval needed), it MUST call this tool immediately. Never ask "want me to notify you?" — just send. The founder reviews and acts via email. All tools must chain.

Channels: webhook (JSON POST), slack (webhook URL), email (SMTP). Use for: governance alerts, deployment notifications, breaking change warnings.

IMPORTANT - Email context rules: Every email must be self-contained and actionable. The recipient reads on mobile and needs to know exactly what to do without opening another app.

  • Subject: lead with [ACTION TYPE] bracket, include enough context to triage from inbox

  • Body: include WHAT happened, WHY it matters, WHAT to do next, and relevant links

  • Never send bare IDs or technical state without human-readable context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNowebhook, slack, or email.webhook
messageNoNotification body. Must include full context (see rules above).
webhook_urlNoURL for webhook/slack channels.
subjectNoSubject line (email only). Use [ACTION], [INFO], [ALERT] prefix.
event_typeNoEvent category for filtering.
toNoRecipient email address (email only). Overrides default DELIMIT_SMTP_TO. Send to any address - leave empty for default.
from_accountNoSender account key from ~/.delimit/secrets/smtp-all.json (e.g. 'notifications@example.com'). Email only. Optional inbox-executor binding (LED-1129 Phase 1, no auto-execution yet):.
draft_kindNoOne of github_comment, social_post, ledger_done, notify_routing_update, deploy_publish_prevalidated_artifact. When set, registers a signed draft in the local SQLite registry so a future executor can match founder Ship-it replies against it.
draft_payloadNoThe action contents (e.g. {"body": "..."} for github_comment). JSON string or dict. Required when draft_kind is set.
draft_targetNoWhere the action lands (e.g. {"repo":"x/y","issue":1}). JSON string or dict. Required when draft_kind is set.
led_refNoOptional LED-XXXX tag tying the draft to its tracking item. Surfaced in subject-line matching by the executor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses side effects: gated by require_premium, sends network messages via different channels, and chaining with inbox daemon. Could mention error handling or rate limits but still strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (when to use, channels, auto-trigger rule, email rules). Slightly verbose but every sentence adds value. Could be more concise while retaining completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, side effects, parameter details, and email formatting. Since no output schema provided, description adequately compensates. Missing error handling or rate limits but still comprehensive for a notification tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage, but description adds value beyond schema: email context rules, subject prefix convention, draft parameters detailed, and message must include full context. Richly enhances understanding of each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sends a notification via webhook/Slack/email and distinguishes from siblings: delimit_notify_routing configures rules, delimit_notify_inbox reads inbound, this sends one outbound.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use (owner action required) and when-not-to-use (SIEM-class streaming or multi-routing config) with sibling alternatives. Also includes an auto-trigger rule: call immediately without asking.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server