Skip to main content
Glama

mavis_session_abort

Abort a running session to immediately stop its ongoing tasks and free system resources.

Instructions

Abort a running session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID to abort

Implementation Reference

  • The execMavis function is the actual handler that spawns the mavis CLI process with the args built by mavis_session_abort's buildArgs. It runs 'mavis session abort <sessionId>' and returns the raw stdout output.
    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 for mavis_session_abort: requires a single string field 'sessionId'.
    inputSchema: z.object({
      sessionId: z.string().describe('Session ID to abort')
    }),
  • src/index.js:161-170 (registration)
    Tool registration for mavis_session_abort. It's defined as an entry in the 'tools' array with 'execFn: execMavis', 'outputMode: OUTPUT_RAW', and a buildArgs function that constructs ['session', 'abort', sessionId].
    {
      name: 'mavis_session_abort',
      description: 'Abort a running session.',
      inputSchema: z.object({
        sessionId: z.string().describe('Session ID to abort')
      }),
      execFn: execMavis,
      outputMode: OUTPUT_RAW,
      buildArgs: ({ sessionId }) => ['session', 'abort', sessionId]
    },
  • The runTool helper orchestrates tool execution. It calls buildArgs to get the CLI args, then invokes execMavis (since mavis_session_abort specifies execFn), and returns the raw output string.
    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 present, so the description bears full burden. It states the action but does not disclose consequences (e.g., data loss, irreversibility, permission requirements).

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?

The description is a single, front-loaded sentence that immediately conveys the tool's purpose with no extraneous words.

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?

For a simple tool with one parameter and no output schema, the description covers the core purpose but lacks behavioral details like side effects or prerequisites.

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 provides a description for the only parameter ('Session ID to abort'), achieving 100% coverage. The tool description adds no extra meaning beyond this, meeting the baseline.

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 ('Abort') and resource ('running session'), clearly distinguishing it from other session-related tools like mavis_session_list or mavis_session_new.

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, nor any context about prerequisites or typical scenarios.

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