Skip to main content
Glama

vibe_help

Read-onlyIdempotent

View all available /vibe commands for the social layer of AI coding, enabling DMs, presence, discovery, and multiplayer games.

Instructions

Show available /vibe commands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main implementation of vibe_help. Defines the tool (name 'vibe_help', description, empty inputSchema) and exports an async handler that returns a markdown table of all /vibe commands along with the current user's identity.
    /**
     * vibe help — Quick reference for /vibe commands
     */
    
    const config = require('../config');
    
    const definition = {
      name: 'vibe_help',
      description: 'Show available /vibe commands',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    };
    
    async function handler() {
      const handle = config.getHandle();
      const identity = handle ? `You're **@${handle}**` : 'Not signed in — run `vibe init`';
    
      return {
        display: `## /vibe — ${identity}
    
    | Command | What it does |
    |---------|-------------|
    | \`vibe\` | Join the room, see who's online, check inbox |
    | \`vibe who\` | See who's building right now |
    | \`vibe dm @handle "msg"\` | Send a direct message |
    | \`vibe inbox\` | Check your messages |
    | \`vibe status shipping\` | Set your mood (shipping, thinking, afk, debugging, pairing, deep) |
    | \`vibe ship "what you built"\` | Announce something you shipped |
    | \`vibe discover\` | Find people building similar things |
    | \`vibe help\` | This screen |
    
    **Install:** \`claude mcp add vibe -- npx -y slashvibe-mcp\`
    **Docs:** slashvibe.dev`
      };
    }
    
    module.exports = { definition, handler };
  • Input schema for vibe_help — no parameters (empty properties object). The tool is purely informational.
    const definition = {
      name: 'vibe_help',
      description: 'Show available /vibe commands',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    };
  • index.js:174-174 (registration)
    Registration of the vibe_help tool in the tools map — maps 'vibe_help' to require('./tools/help') which exports { definition, handler }.
    vibe_help: require('./tools/help'),
  • Safety annotations for vibe_help: readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false (no network calls).
    vibe_help:     { readOnlyHint: true,  destructiveHint: false, idempotentHint: true,  openWorldHint: false },
  • vibe_help is in SKIP_FOOTER_TOOLS list, meaning the ambient presence footer is suppressed for this tool (would be redundant/noisy).
    const SKIP_FOOTER_TOOLS = ['vibe_init', 'vibe_help'];
Behavior3/5

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

Annotations already provide strong behavioral hints (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds no additional behavioral context beyond what is already captured in the annotations. It does not contradict annotations, but it also does not add value (e.g., rate limits, exact return format).

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, well-formed sentence that conveys the tool's purpose efficiently. Every word is meaningful, and there is no extraneous content. It is front-loaded and perfectly concise.

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 (0 parameters, no output schema, rich annotations), the description covers the essential purpose. However, it could be slightly more complete by hinting at what the output looks like (e.g., a list or help text). Nonetheless, it is adequate for an agent to understand the tool's function.

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, and schema coverage is 100% (vacuously). According to the rubric, when there are 0 parameters, the baseline score is 4. The description provides no parameter-specific info, which is acceptable given no parameters exist.

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 'Show available /vibe commands' clearly states the tool's function: it lists the available commands under the /vibe namespace. The verb 'Show' and resource 'available /vibe commands' are specific, and it distinguishes itself from sibling tools (specific commands like vibe_discover) by being the help/overview tool.

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 usage (when one needs to see available commands), but it offers no explicit guidance on when to use this tool versus the siblings, nor does it mention any alternatives or exclusions. The meaning is clear, but the guidance is minimal.

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/VibeCodingInc/vibe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server