Skip to main content
Glama

schedule_notification

Explains how to send a ServiceNow notification at a set time and returns NOT_SUPPORTED with a scheduled-job alternative, since notification rules lack native schedules.

Instructions

[Write] Explain how to send a notification at a set time. ServiceNow notifications are event/condition driven and have no schedule of their own, so this returns NOT_SUPPORTED with the scheduled-job alternative and changes nothing

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": {
      "notification_id": "<notification_id>",
      "schedule": "<schedule>"
    },
    "name": "schedule_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeNoWhether the notification is active
scheduleYesCron expression or ISO date
notification_idYesNotification rule sys_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior1/5

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

The description says the tool 'changes nothing' and returns NOT_SUPPORTED, which directly contradicts the readOnlyHint=false annotation indicating a non-read-only operation. This is a material inconsistency about whether the tool performs a write, so the score is penalized to 1 despite the otherwise useful disclosure that no state is altered.

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 two compact sentences with no wasted wording, and the key outcome (NOT_SUPPORTED, changes nothing) is stated clearly. The '[Write]' prefix is slightly extraneous but does not undermine the overall efficiency.

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 tool with no output schema, the description explains the unusual return behavior (NOT_SUPPORTED) and the fact that no change occurs, which is essential context. It could name the specific scheduled-job alternative tool, but otherwise it gives an agent enough to act correctly.

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 the input schema already documents all three parameters. The description adds no parameter-specific meaning beyond what the schema provides, which is the expected baseline when schema descriptions are complete.

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 description states a specific behavior: it explains how to schedule a notification but actually returns NOT_SUPPORTED because ServiceNow notifications are event/condition driven. This clearly distinguishes it from tools that create or update notifications, though it does not name a specific sibling tool as the alternative.

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?

The description implies the tool is used when someone wants to send a notification at a set time, and it explicitly states that the result is NOT_SUPPORTED with a scheduled-job alternative. It does not give an explicit 'use this tool when…' clause or name the alternative tool, leaving some inference to the agent.

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