Skip to main content
Glama

notifications_send_notification

Send system notifications on macOS with custom titles, messages, and optional sound playback through AppleScript integration.

Instructions

[Notification management] Send a system notification

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNotification title
messageYesNotification message
soundNoPlay sound with notification

Implementation Reference

  • The handler function that generates AppleScript code to display a macOS system notification with the given title, message, and optional sound.
    script: (args) => `
      display notification "${args.message}" with title "${args.title}" ${args.sound ? 'sound name "default"' : ""}
    `,
  • Input schema defining parameters for the notification: required title and message strings, optional sound boolean.
    schema: {
      type: "object",
      properties: {
        title: {
          type: "string",
          description: "Notification title",
        },
        message: {
          type: "string",
          description: "Notification message",
        },
        sound: {
          type: "boolean",
          description: "Play sound with notification",
          default: true,
        },
      },
      required: ["title", "message"],
    },
  • Registers the tool in the MCP server by dynamically constructing the tool name as 'category_script' (e.g., 'notifications_send_notification') and providing schema and description.
    tools: this.categories.flatMap((category) =>
      category.scripts.map((script) => ({
        name: `${category.name}_${script.name}`, // Changed from dot to underscore
        description: `[${category.description}] ${script.description}`,
        inputSchema: script.schema || {
          type: "object",
          properties: {},
        },
      })),
    ),
  • src/index.ts:29-29 (registration)
    Registers the notifications category containing the send_notification script with the MCP server.
    server.addCategory(notificationsCategory);
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Send a system notification' implies a write operation that likely requires permissions and may have side effects (e.g., user disruption), but the description doesn't disclose behavioral traits like authentication needs, rate limits, or what happens when notifications are sent. It's minimally descriptive for a mutation tool.

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

Conciseness5/5

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

The description is extremely concise with just two words in brackets and three words outside: '[Notification management] Send a system notification'. It's front-loaded and wastes no words, though this brevity contributes to gaps in other dimensions. Every sentence (or phrase here) earns its place.

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

Completeness2/5

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

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'system notification' entails, who receives it, potential errors, or return values. For a tool that likely interacts with user interfaces or permissions, more context is needed for effective use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters (title, message, sound) with descriptions and defaults. The description adds no additional meaning beyond what's in the schema, such as formatting constraints or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Send a system notification' states the verb ('send') and resource ('system notification'), but it's vague about what constitutes a 'system notification' and doesn't differentiate from sibling tools like 'notifications_toggle_do_not_disturb'. It's clear enough to understand the basic action but lacks specificity about the notification target or system scope.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for sending notifications, or compare to other notification-related tools. Without any usage context, an agent must infer based on the name alone.

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/joshrutkowski/applescript-mcp'

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