iSuite Operations MCP Server

disable_schedule

Disable an active schedule to pause automatic execution without deleting it. Record reason in audit log for accountability.

Instructions

Disable an active iSuite schedule to pause automatic execution without deleting it.

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": {
      "scheduleId": "<scheduleId>"
    },
    "name": "disable_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`scheduleId`	Yes	The unique schedule ID to disable.
`reason`	No	Reason for disabling (recorded in audit log).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states that disabling pauses execution and does not delete, which is key. However, it omits whether the operation is reversible, requires special permissions, or affects currently running jobs. Adequate but not detailed.

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?

Single sentence with no waste. Directly states the action, target, and effect without redundant information.

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 simple state-change tool, the description covers the essential purpose. It could mention that the reason is recorded in an audit log (as implied by the parameter), and that the schedule can be re-enabled. No output schema exists, so return values are not expected. Solid overall.

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 baseline is 3. Description adds no extra meaning to the parameters beyond what the schema provides. The reason parameter is hinted in the audit log context, but not explicitly described.

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?

The description clearly states the verb 'Disable', the resource 'active iSuite schedule', and the outcome 'pause automatic execution without deleting it'. It distinguishes from related tools like enable_schedule.

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?

No explicit guidance on when to use this tool versus alternatives like enable_schedule or delete_schedule. The phrase 'without deleting it' hints at a contrast, but no clear when-to-use or when-not-to instructions.

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