Skip to main content
Glama

notify

Displays a macOS notification to surface a message or alert locally, with optional title and subtitle fields.

Instructions

Show a macOS notification. macOS shows the applesauce icon, so never put 'applesauce' in the text. Give a 'title' only when it adds information, like an event name or a headline. Leave it out for a short message: macOS then shows the app name as the title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional bold first line, like an event name or a headline.
messageYesNotification text.
subtitleNoOptional line under the title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already pin the profile (non-read-only, non-destructive, closed-world), and the description usefully discloses what the user actually sees: the applesauce icon, and the app name substituted as title when title is omitted. It stops short of delivery semantics, such as whether the call is fire-and-forget, whether anything is returned, or what happens if notification permission is denied.

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?

Purpose is front-loaded and the remaining sentences each carry a distinct constraint; nothing is padding. The phrase 'in the text' is slightly ambiguous about whether it covers title and subtitle or only message, a small clarity cost in otherwise tight prose.

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?

For a simple three-parameter, single-required-field tool with full schema coverage and no output schema, the description covers platform, visual side effect, and title handling. Only minor gaps remain around error conditions and whether any response is produced.

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 coverage is 100%, so all three parameters are already documented. The description adds real meaning for title by prescribing when to include versus omit it, but subtitle is left entirely to the schema, so the addition is partial rather than comprehensive.

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?

Opens with a specific verb and resource: 'Show a macOS notification.' An agent immediately knows what the tool produces. No sibling performs notifications, so no differentiation is required, but neither is it offered.

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?

Gives explicit conditional guidance on the title parameter ('Give a title only when it adds information... Leave it out for a short message'), which is the main decision an agent faces here. No exclusions or alternatives are named, though none exist among the siblings.

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