Skip to main content
Glama

mavis_agent_list

Retrieve a list of all available Mavis agents, including built-in and custom agents, to identify which agents can be used for tasks.

Instructions

List all available Mavis agents (built-in and custom).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool definition for 'mavis_agent_list' in the tools array. handler logic: builds CLI args ['agent', 'list'] which is executed via execMavisJSON (the default, since no execFn is specified), calling the Mavis CLI binary to list all agents.
    {
      name: 'mavis_agent_list',
      description: 'List all available Mavis agents (built-in and custom).',
      inputSchema: z.object({}),
      buildArgs: () => ['agent', 'list']
    },
  • src/index.js:484-495 (registration)
    The tool is registered in the MCP server by being added to the 'tools' array (line 98-467) and then loaded into a toolMap (line 484) used by the CallToolRequestSchema handler (line 494-509) to dispatch incoming tool calls.
    this.toolMap = new Map(tools.map(t => [t.name, t]));
    
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: tools.map(t => ({
        name: t.name,
        description: t.description,
        inputSchema: normalizeObjectSchema(t.inputSchema),
      })),
    }));
    
    this.server.setRequestHandler(CallToolRequestSchema, async request => {
      const { name, arguments: args } = request.params;
  • The runTool helper function that executes the tool. For mavis_agent_list (no execFn defined), it uses execMavisJSON to call the Mavis CLI with args ['agent', 'list'] and returns the JSON output.
    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 }];
      });
    }
  • The execMavisJSON helper function that calls the Mavis CLI binary and parses JSON output. Since mavis_agent_list has no execFn, this is the default execution path.
    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);
        }
      });
    }
Behavior2/5

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

No annotations are provided, so the description must compensate. It only states the listing action without disclosing safety (e.g., read-only) or any behavioral traits like pagination 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.

Conciseness5/5

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

Single sentence, 8 words, no wasted text. Front-loaded with verb and resource, perfectly concise for a simple list tool.

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

Completeness4/5

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

Given the tool's simplicity (no params, no output schema), the description adequately states what the tool does. It could hint at the output format, but overall sufficient for context.

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 tool has zero parameters, so per guidelines baseline is 4. The description does not need to add parameter details, and the schema already covers all aspects.

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 tool lists all Mavis agents, specifying both built-in and custom, distinguishing it from sibling 'mavis_agent_info' which provides details on a single agent.

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?

No explicit guidance on when to use this tool versus alternatives like mavis_agent_info; usage is implied by the purpose but lacks when-not or alternative references.

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