Skip to main content
Glama

mavis_cron_delete

Delete a scheduled cron task owned by a specific agent in the multi-agent system.

Instructions

Delete a cron job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNameYesAgent name or ID that owns the cron task
cronNameYesCron task name

Implementation Reference

  • src/index.js:334-344 (registration)
    Tool definition/registration for mavis_cron_delete. Defines name, description, input schema (agentName, cronName), sets execFn to execMavis, outputMode to OUTPUT_RAW, and buildArgs to construct CLI arguments ['cron', 'delete', agentName, cronName].
    {
      name: 'mavis_cron_delete',
      description: 'Delete a cron job.',
      inputSchema: z.object({
        agentName: z.string().describe('Agent name or ID that owns the cron task'),
        cronName: z.string().describe('Cron task name')
      }),
      execFn: execMavis,
      outputMode: OUTPUT_RAW,
      buildArgs: ({ agentName, cronName }) => ['cron', 'delete', agentName, cronName]
    },
  • The execMavis function that executes the tool logic. Spawns the MAVIS_BIN CLI process with the constructed args (['cron', 'delete', agentName, cronName]), captures stdout/stderr, resolves with trimmed stdout on success, rejects with stderr on error.
    function execMavis(args, input = '') {
      return new Promise((resolve, reject) => {
        const SESSION_COMMANDS = new Set(['communication', 'session', 'spawn']);
        const sessionId = process.env.__MAVIS_PARENT_SESSION_ID;
        const subcmd = args[0];
        const needsSession = SESSION_COMMANDS.has(subcmd) && sessionId;
        const finalArgs = needsSession ? [...args, '--session', sessionId] : args;
        const proc = spawn(MAVIS_BIN, finalArgs, { stdio: ['pipe', 'pipe', 'pipe'] });
        let stdout = '';
        let stderr = '';
    
        proc.stdout.on('data', d => stdout += d.toString());
        proc.stderr.on('data', d => stderr += d.toString());
        proc.on('close', code => {
          if (code === 0) resolve(stdout.trim());
          else reject(new Error(stderr.split('\n')[0] || `exit code ${code}`));
        });
        proc.on('error', reject);
    
        if (input) proc.stdin.write(input), proc.stdin.end();
      });
    }
  • Input schema definition for mavis_cron_delete. Uses Zod to define two required string fields: agentName and cronName.
    inputSchema: z.object({
      agentName: z.string().describe('Agent name or ID that owns the cron task'),
      cronName: z.string().describe('Cron task name')
    }),
  • The runTool function that invokes the tool. For mavis_cron_delete, it uses execMavis (since execFn is set), passes the built args, and returns the raw string result (since outputMode is OUTPUT_RAW).
    function runTool(spec, parsedArgs) {
      const { execFn, outputMode, stdin, buildArgs } = spec;
      const args = buildArgs(parsedArgs);
      const input = typeof stdin === 'function' ? stdin(parsedArgs) : stdin;
    
      const execPromise = execFn
        ? execMavis(args, input || '')
        : execMavisJSON(args);
    
      return execPromise.then(result => {
        const text = outputMode === OUTPUT_RAW
          ? (result || '')
          : JSON.stringify(result, null, 2);
        return [{ type: 'text', text }];
      });
    }
Behavior2/5

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

No annotations are provided, and the description only states 'Delete a cron job' without any additional behavioral context such as irreversibility, permissions, or side effects.

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?

The description is extremely concise with no wasted words. However, it is somewhat under-specified for a delete operation, so a perfect score is not warranted.

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?

The tool has no output schema and the description provides no information on return values, success indicators, or error conditions. For a destructive operation, more context is needed.

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 both parameters, so the description adds no extra meaning beyond what is already in the schema. Baseline 3 applies.

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 'Delete a cron job' with specific verb and resource. It distinguishes from sibling tools mavis_cron_create and mavis_cron_list which perform different operations.

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 is provided on when to use this tool, prerequisites, or alternatives. The agent must infer the usage context from the name alone.

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/Cunning-Kang/mavis-mcp-server'

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