Skip to main content
Glama
Sign In
node-notifier

node-notifier

by Ardor303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_notification_profiles

Read-only

List built-in and custom notification profiles with their names, kinds, titles, and descriptions to read current configuration and identify the profile name to use in notify.profile.

Instructions

List available built-in and custom notification profiles with their names, kinds, titles and descriptions. Reads current configuration; use the returned name in notify.profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_notification_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds scope disclosure ('built-in and custom') and confirms it reads live configuration rather than a cache, plus the downstream dependency on notify.profile. It stops short of describing ordering or whether profiles can be absent.

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?

Two sentences with no filler: the first describes the resource and returned fields, the second gives behavior and the follow-up action. Content is front-loaded and every clause earns its place.

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?

With no output schema, the description usefully enumerates the returned fields (names, kinds, titles, descriptions), which is the key compensation. Nothing needed to invoke the tool is missing; only minor details like ordering or empty-result behavior are unstated.

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?

There are zero parameters, so the baseline is 4 and no parameter semantics are needed. The description does not invent or reference any inputs.

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 ('List') and resource ('notification profiles'), and narrows scope to 'built-in and custom'. The resource is clearly distinct from the sibling resources (notifications, notify), so an agent can tell this apart without opening a schema.

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

Usage Guidelines5/5

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

Gives both the immediate purpose ('Reads current configuration') and the explicit next step ('use the returned name in notify.profile'), which is the routing information an agent needs. For a zero-parameter read tool there is little else to disambiguate.

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