Skip to main content
Glama

mavis_skill_list

Retrieve a list of all installed Mavis skills, including global and agent-specific ones, to understand what capabilities are available.

Instructions

List all installed Mavis skills (global and agent-specific).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:348-353 (registration)
    Tool registration for mavis_skill_list: part of the tools array, defines name, description, empty input schema (no params), and buildArgs that constructs CLI args ['skill', 'list'] to the Mavis binary. No custom execFn so runTool uses execMavisJSON by default.
    {
      name: 'mavis_skill_list',
      description: 'List all installed Mavis skills (global and agent-specific).',
      inputSchema: z.object({}),
      buildArgs: () => ['skill', 'list']
    },
  • Generic tool handler (runTool) used by mavis_skill_list. Since mavis_skill_list has no execFn, it takes the execMavisJSON branch: executes 'mavis skill list', parses JSON output, and stringifies the result as text.
    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 }];
      });
    }
  • execMavis helper: spawns the MAVIS_BIN ('/Users/cunning/.mavis/bin/mavis') with args. For mavis_skill_list, subcmd='skill' which is not in SESSION_COMMANDS, so no session flag is injected.
    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();
      });
    }
  • execMavisJSON helper: wraps execMavis to parse the CLI output as JSON, used by mavis_skill_list since it has no execFn.
    function execMavisJSON(args) {
      return execMavis(args).then(raw => {
        try {
          return JSON.parse(raw);
        } catch {
          const jsonStart = raw.indexOf('{');
          return JSON.parse(jsonStart >= 0 ? raw.slice(jsonStart) : raw);
        }
      });
    }
  • Input schema for mavis_skill_list: empty object (z.object({})), meaning no parameters are accepted.
    inputSchema: z.object({}),
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'list' without mentioning side effects, permissions, rate limits, or return format, which is insufficient.

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?

A single, clear sentence with no fluff. Every word adds value.

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?

The description is minimal and does not explain return values or what constitutes a 'skill'. Given no output schema, some explanation of the expected return would be beneficial. It is adequate but has gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so baseline is 4. The description adds no parameter information, but none is needed since there are no parameters to document.

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 'list', the resource 'installed Mavis skills', and adds a qualifier 'global and agent-specific' which distinguishes it from the sibling 'mavis_skill_info' that likely retrieves details of a single skill.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (to list all skills) but does not explicitly exclude cases or compare to alternatives. Siblings like 'mavis_skill_info' exist but are not mentioned.

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