iSuite Operations MCP Server

list_schedules

Retrieve all defined iSuite job schedules, with optional filters by status, job type, and result limit.

Instructions

List all defined iSuite job schedules.

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_schedules"
  }
}

Input Schema

Name	Required	Description
`status`	No	Filter by schedule status (default 'all').
`jobType`	No	Filter by associated job type.
`limit`	No	Maximum results to return (default 100).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states 'list all defined' but the schema includes filters (status, jobType, limit), which is not mentioned. There is no information about read-only nature, pagination, or potential performance implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, which earns its place. However, it is too terse and could benefit from additional context without becoming verbose.

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?

Given the tool has 3 optional filter parameters and no output schema, the description lacks details on filtering behavior, default status, and output format. It does not differentiate well from sibling list tools that might also return schedule-like objects.

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?

The input schema has 100% description coverage for its 3 parameters, so the schema already documents them. The description adds no additional meaning beyond the schema since it only says 'list all defined schedules' without explaining how parameters modify the result.

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 uses a specific verb ('List') and resource ('iSuite job schedules'), clearly indicating the tool's purpose. It distinguishes from the sibling tool 'get_schedule' which retrieves a single schedule, though it does not explicitly differentiate from other list tools.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'list_batch_jobs' or 'list_running_jobs'. There are no usage conditions, prerequisites, or exclusions mentioned.

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