Skip to main content
Glama

mavis_skill_info

Retrieves detailed information about a skill, including its description, triggers, and commands, for a specified agent.

Instructions

Get detailed info about a specific skill (description, triggers, commands).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillNameYesSkill name
agentNameNoAgent name to scope the lookup

Implementation Reference

  • Tool definition and input schema for mavis_skill_info. Defines skillName (required) and agentName (optional). buildArgs constructs CLI args: 'skill show <skillName>' with optional '--agent <agentName>'.
      name: 'mavis_skill_info',
      description: 'Get detailed info about a specific skill (description, triggers, commands).',
      inputSchema: z.object({
        skillName: z.string().describe('Skill name'),
        agentName: z.string().optional().describe('Agent name to scope the lookup')
      }),
      buildArgs: ({ skillName, agentName }) => {
        if (!skillName) throw new Error('skillName is required');
        const args = ['skill', 'show', skillName];
        if (agentName) args.push('--agent', agentName);
        return args;
      }
    },
  • Generic tool handler runner. For mavis_skill_info, since no execFn is defined on the spec, it falls through to execMavisJSON (the else branch), which calls execMavis then JSON.parses the 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 }];
      });
    }
  • src/index.js:473-510 (registration)
    MCP server registration. tools array (containing mavis_skill_info) is mapped into a toolMap, exposed via ListToolsRequestSchema, and handled via CallToolRequestSchema which calls runTool.
    class MavisServer {
      constructor() {
        this.server = new Server(
          {
            name: 'mavis-mcp-server',
            version: '1.2.0',
            description: 'Mavis agent team — multi-agent orchestration via MCP',
          },
          { capabilities: { tools: {} } }
        );
    
        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;
          const tool = this.toolMap.get(name);
    
          if (!tool) {
            return { content: [{ type: 'text', text: `Error: unknown tool "${name}"` }], isError: true };
          }
    
          try {
            const parsedArgs = tool.inputSchema.parse(args || {});
            const results = await runTool(tool, parsedArgs);
            return { content: results };
          } catch (err) {
            return { content: [{ type: 'text', text: `Mavis error: ${err.message}` }], isError: true };
          }
        });
      }
  • Helper functions: execMavis spawns the mavis CLI binary; execMavisJSON wraps it to parse JSON output. mavis_skill_info uses execMavisJSON (no execFn on spec).
    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 exist, so description carries full burden. It discloses that the tool retrieves details (description, triggers, commands), implying a read-only operation. However, it does not mention authentication, rate limits, 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?

Single sentence, directly states purpose and content. Efficient but could benefit from slightly more structure (e.g., listing each returned component separately).

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?

Given no output schema, the description explains the return type (description, triggers, commands). It does not detail optional parameter agentName's effect or mention if additional fields exist.

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?

Schema description coverage is 100%, meaning parameters already have descriptive names and basic descriptions. The description adds no additional semantic value beyond the schema.

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 it gets detailed info about a specific skill and enumerates what that info includes (description, triggers, commands). This distinguishes it from sibling mavis_skill_list which likely returns a list of skills without details.

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 versus alternatives like mavis_skill_list. The description does not specify prerequisites or contexts for use.

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