Skip to main content
Glama

ninja_list_scheduled_tasks

Retrieve a complete list of all scheduled automation tasks to review and manage their execution.

Instructions

List all scheduled automation tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'ninja_list_scheduled_tasks' tool. It calls client.get('/tasks') to list all scheduled automation tasks via the NinjaOne API.
    {
      tool: {
        name: 'ninja_list_scheduled_tasks',
        description: 'List all scheduled automation tasks.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/tasks'),
    },
  • Input schema for ninja_list_scheduled_tasks — an empty object (no parameters required).
    inputSchema: { type: 'object', properties: {} },
  • The tool is registered in ALL_TOOLS via the systemTools array export, which is collected along with other tool modules.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • src/index.ts:24-24 (registration)
    The toolMap is built in the MCP server entry point by mapping tool names to handlers, enabling dispatch of 'ninja_list_scheduled_tasks' calls.
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
  • The NinjaOneClient.get() method used by the handler to make the GET /tasks API request.
    async get<T = unknown>(path: string, params?: Record<string, unknown>): Promise<T> {
      try {
        const res = await this.http.get<T>(path, {
          params,
          headers: await this.authHeader(),
        });
        return res.data;
      } catch (err) {
        throw new Error(`GET ${path} failed: ${apiError(err)}`);
      }
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as pagination, scoping, or side effects. The minimal description does not compensate for the lack of annotations.

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?

Single sentence, efficient and to the point. However, could be expanded with key details without losing conciseness.

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

Completeness3/5

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

Description is minimal and does not explain what fields are returned or how results are structured. Lacks completeness for a simple list tool without output schema or annotations.

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?

No parameters exist, and schema description coverage is 100% (empty schema). Baseline 3 applies; description adds no extra parameter meaning.

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 uses a specific verb 'List' and resource 'scheduled automation tasks', clearly distinguishing it from sibling list tools like ninja_list_activities or ninja_list_devices.

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 guidance when to use this tool over other listing tools. No explicit context or alternatives provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Allied-Business-Solutions/ninjaone-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server