Skip to main content
Glama

Show a notification

notify

Display a macOS notification when a long-running job finishes, so you know when to return. Provide a bold title and message text; nothing else on your system changes.

Instructions

Show a macOS notification on the user's screen, e.g. when a long job finishes so they know to come back. It changes nothing else.

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": {
      "title": "<title>",
      "message": "<message>"
    },
    "name": "notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesthe notification's bold first line
messageYesthe text under the title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.3
    • addedInput schema / properties / message / description
      Added value: +"the text under the title"
    • addedInput schema / properties / message / maxLength
      Added value: +500
    • addedInput schema / properties / title / description
      Added value: +"the notification's bold first line"
    • addedInput schema / properties / title / maxLength
      Added value: +100
  2. First observedv0.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by clarifying the side-effect scope — 'It changes nothing else' — which resolves the ambiguity created by readOnlyHint=false (the tool does something, but mutates no state). It does not mention OS notification permission prompts or whether the call blocks, which are the remaining gaps.

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?

A single sentence plus one short clarifying clause; the purpose and platform lead, and the usage example follows. Every clause earns its place with no redundant restatement of the title.

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 two-parameter, non-destructive display tool with full schema coverage and annotations present, the definition is essentially complete. Only minor operational details — permission requirements or behavior on non-macOS hosts — are absent, which is a small gap rather than a blocker.

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%, with both parameters documented ('bold first line', 'text under the title') and length limits stated. The description adds no further meaning about title/message beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Show a macOS notification on the user's screen') with the platform scoped explicitly. No sibling tool in the list deals with notifications, so an agent can route to it without opening the schema.

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 a concrete when-to-use scenario ('when a long job finishes so they know to come back'), which is exactly the kind of guidance an agent needs to decide between notifying and staying silent. It stops short of explicit when-not conditions or named alternatives, but none of the siblings overlap in behavior.

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