Skip to main content
Glama

delimit_notify

Send automated notifications for governance alerts, deployment decisions, and approval requests. Triggers instantly when owner action is required.

Instructions

Send a notification (Pro).

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 notification. The founder reviews and acts via email. All tools must chain automatically.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses channels, email formatting rules, and auto-trigger behavior, but omits details like error handling, permission requirements, or confirmation behavior.

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 sections for auto-trigger, channels, and email rules. Some sentences could be more concise, but overall it is clear and organized.

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 when to use, channels, email formatting, and auto-trigger rules. Missing details like error handling, but output schema exists to describe return values, so it is reasonably complete.

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

Parameters4/5

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

Schema coverage is 100% with descriptions, baseline 3. The description adds useful context beyond schema, such as email prefix rules for subject and where to find sender account keys, enhancing parameter understanding.

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

Purpose4/5

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

The description clearly states it sends notifications via webhook, slack, or email, and lists use cases. However, it does not explicitly differentiate from sibling notification tools like delimit_notify_inbox or delimit_notify_routing.

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

Usage Guidelines4/5

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

Includes an auto-trigger rule specifying when the AI must call this tool (when owner action needed) and a list of use cases. However, it lacks explicit when-not-to-use guidance and does not mention alternatives.

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