Skip to main content
Glama
Sign In
mcp-server-macos

mcp-server-macos

by JeanExtreme002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Send a notification

send_notification

Shows a notification on a Mac in the top-right corner and Notification Center, with optional title, subtitle, and alert sound.

Instructions

Show a notification on this Mac, in the top-right corner of the screen and in Notification Center.

macOS shows it as coming from Script Editor. Text over 4096 characters is clipped. Don't put a secret in a notification: other processes of the user can see its text while it's being posted.

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": "send_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
soundNoThe name of a system alert sound to play, e.g. 'Glass', 'Ping' or 'Basso'. Silent by default.
titleNoThe title, in bold above the text.
messageYesThe notification's text.
subtitleNoA line between the title and the text.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

The description goes well beyond the annotations, disclosing sender attribution ('macOS shows it as coming from Script Editor'), a hard truncation limit (4096 characters clipped), and a security caveat that other user processes can read the text while it is posted. These are exactly the side-effect and visibility traits an agent cannot get from readOnlyHint/destructiveHint alone.

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?

Three short sentences, front-loaded with what the tool does, then attribution, limit, and security warning in descending priority. No sentence is filler.

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

Completeness5/5

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

An output schema exists so return values need no explanation, and the description covers the remaining gaps an agent needs: where the notification appears, how it is attributed, truncation behavior, and the privacy risk. Nothing material is missing for a 4-parameter tool.

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%, so the baseline is 3, but the description adds real meaning for the 'message' parameter: the 4096-character clipping behavior, which the schema only bounds with minLength 1 and no maximum. Sound, title, and subtitle semantics are left entirely to the schema.

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 opening sentence names a specific verb ('Show a notification') and resource, plus concrete placement ('top-right corner of the screen and in Notification Center'). It is unambiguous against the only sibling, get_system_info, but it does not explicitly differentiate itself from anything, which keeps it just short of a 5.

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

Usage Guidelines3/5

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

There is no when-to-use vs. when-not-to-use guidance relative to alternatives; the only constraint given is content-related ('Don't put a secret in a notification'). Usage is implied by the tool name and purpose rather than stated as selection criteria.

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

Deploy Server

Other Tools