Skip to main content
Glama

mavis_config_show

View the current configuration of the Mavis daemon, including models, provider, and nexus settings.

Instructions

Show current Mavis daemon configuration (models, provider, nexus settings).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition for 'mavis_config_show'. The handler is implicit: it has no custom execFn, so runTool uses execMavisJSON (line 84) which executes mavis CLI with buildArgs = ['config', 'show'] and parses the JSON output. No schema validation beyond an empty object.
    {
      name: 'mavis_config_show',
      description: 'Show current Mavis daemon configuration (models, provider, nexus settings).',
      inputSchema: z.object({}),
      buildArgs: () => ['config', 'show']
    },
  • Input schema for mavis_config_show: z.object({}) — no arguments expected.
    {
      name: 'mavis_config_show',
      description: 'Show current Mavis daemon configuration (models, provider, nexus settings).',
      inputSchema: z.object({}),
      buildArgs: () => ['config', 'show']
    },
  • src/index.js:484-492 (registration)
    Tools are registered in MavisServer constructor via this.toolMap = new Map(tools.map(t => [t.name, t])) (line 484) and served through ListToolsRequestSchema handler (line 486).
    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),
      })),
    }));
  • runTool is the generic handler runner. For mavis_config_show (no custom execFn), it calls execMavisJSON(args) which runs 'mavis config show' and parses 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);
  • execMavis helper spawns the mavis CLI binary with arguments and captures stdout.
    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();
      });
    }
Behavior3/5

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

No annotations are provided, so the description bears full behavioral transparency burden. It indicates a read operation via 'Show', but does not mention side effects, authentication needs, or rate limits. This is adequate for a simple read-only tool.

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, 9-word sentence with parenthetical detail. Every word earns its place. No redundant or vague phrasing.

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

Completeness5/5

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

For a no-parameter, read-only tool, the description sufficiently conveys what it does. The absence of an output schema is acceptable given typical expectations for a config show command.

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 zero parameters with 100% coverage, so the description need not add parameter info. Baseline of 3 is appropriate.

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?

Description clearly states the verb 'Show' and the resource 'Mavis daemon configuration', with a parenthetical list of contents (models, provider, nexus settings). This distinguishes it from sibling tools like mavis_status or mavis_session_info.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it contrast with sibling tools. However, the purpose itself implies usage for viewing configuration, so it avoids misleading the agent.

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