OrgLines

Cancel scheduled notification

cancel_scheduled_notification

Destructive

Cancel one of the caller's scheduled notifications by id (soft — sets status to 'cancelled' and stops future delivery). Pass 'skip_next_only': true to instead skip just the NEXT occurrence of a recurring series and keep it running (advances next_send_at past the upcoming fire). Only the caller's own notification is reachable. CONFIRMATION: this tool runs immediately when the caller asks for it — it writes only their own record, and they can undo it from this same surface, so the request is taken as the instruction. You get an ordinary result, not a plan_token. Everything destructive, outbound or financial still proposes and waits.

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>"
    },
    "name": "cancel_scheduled_notification"
  }
}

Input Schema

Name	Required	Description	Default
`skip_next_only`	No
`notification_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: explains that cancellation is soft (status set to 'cancelled'), that future delivery stops, that skip_next_only advances next_send_at past the upcoming fire, and that the action is undoable from the same surface. The confirmation paragraph clarifies execution semantics ('runs immediately', 'ordinary result, not a plan_token'), which is exactly the kind of context annotations cannot carry.

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 and default behavior are front-loaded in the first sentence, then the alternate mode. The CONFIRMATION block is longer than strictly necessary for this single tool, but it conveys useful execution-policy context rather than filler.

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 mutation with annotations but no output schema, it covers scope, semantics, reversibility, and execution model. What remains unstated is the result shape beyond 'ordinary result' and how failures (already sent, not found, not owner) are surfaced.

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?

With 0% schema description coverage, the description must carry the load, and it does: skip_next_only's behavior is spelled out in detail, and notification_id is described as identifying one of the caller's own notifications. Minor gap: no mention of accepting either an integer or a string id, nor of error behavior for an already-sent or unknown id.

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 ('Cancel one of the caller's scheduled notifications by id') and immediately clarifies the default soft-cancel semantics versus the skip-next-occurrence mode. An agent can distinguish this from listing/getting notifications and from a hard-delete 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 explicit mode selection guidance: omit skip_next_only to end the series, pass true to skip only the next fire and keep the recurrence running. It also bounds scope ('Only the caller's own notification is reachable'). It does not name sibling tools such as mail_cancel_scheduled, but the in-tool alternatives are fully covered.

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

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?