Skip to main content
Glama
Sign In
@nexalware/mcp

@nexalware/mcp

Official
by nexalware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_schedule

Cancel a device's scheduled slot by providing its public device ID and slot number (0-4). Use it to remove an unwanted or outdated schedule from a device.

Instructions

Cancel a schedule slot.

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": {
      "deviceId": "<deviceId>",
      "slot": "<slot>"
    },
    "name": "delete_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesWhich schedule slot (0-4) to cancel.
deviceIdYesThe device's public id, e.g. dev_a1b2c3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a destructive mutation. It does not state whether canceling clears the slot, deletes it permanently, is reversible, or what permissions are required.

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?

A single short sentence with no filler, front-loading the verb and resource. It is efficient, though the extreme brevity leaves no room for useful context.

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

Completeness2/5

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

For a destructive, annotation-free mutation tool with no output schema, the description is too thin: it omits reversibility, permission requirements, and result behavior. The schema documents its two parameters well, but the behavioral gap remains.

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% and both parameters are documented with types, range, and an example device id format. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (Cancel) and resource (schedule slot), which distinguishes it from sibling create_schedule, update_schedule, and list_schedules. However, 'schedule slot' is not defined and no scope details are given, so it falls short of a full 5.

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

Usage Guidelines2/5

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

There is no guidance on when to cancel a slot versus calling update_schedule or create_schedule, no prerequisites, and no exclusions. The agent must infer usage entirely from the name.

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