Skip to main content
Glama

vibe_discover

Read-onlyIdempotent

Find developers building similar projects using suggest, search, or active commands.

Instructions

Find people building similar things. Commands: suggest, search, active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandNoDiscovery command to run
queryNoSearch query (for search command)

Implementation Reference

  • Input schema definition for vibe_discover. Defines the 'command' enum (suggest, search, active) and optional 'query' string for the search command.
    const definition = {
      name: 'vibe_discover',
      description: 'Find people building similar things. Commands: suggest, search, active.',
      inputSchema: {
        type: 'object',
        properties: {
          command: {
            type: 'string',
            enum: ['suggest', 'search', 'active'],
            description: 'Discovery command to run'
          },
          query: {
            type: 'string',
            description: 'Search query (for search command)'
          }
        }
      }
    };
  • Main handler function for vibe_discover. Implements three commands: 'suggest'/'active' (shows online/recently active users), 'search' (filters users by query matching handle or one_liner/note), and default (help text listing commands). Returns formatted markdown display.
    async function handler(args) {
      const initCheck = requireInit();
      if (initCheck) return initCheck;
    
      const myHandle = config.getHandle();
      const command = args.command || 'suggest';
    
      let display = '';
    
      try {
        // Get active users + recently active for richer discovery
        const users = await store.getActiveUsers({ includeRecent: true });
        const recentUsers = users._recent || [];
        const others = users.filter(u => u.handle !== myHandle);
        const recentOthers = recentUsers.filter(u => u.handle !== myHandle);
    
        switch (command) {
          case 'suggest':
          case 'active': {
            if (others.length === 0 && recentOthers.length === 0) {
              display = `## Discover
    
    _No one's been active recently. Be the first!_`;
            } else {
              if (others.length > 0) {
                display = `## Online Now\n\n`;
                for (const u of others) {
                  display += `**@${u.handle}**\n`;
                  display += `${u.note || u.one_liner || 'Building something'}\n`;
                  display += `_${formatTimeAgo(u.lastSeen)}_\n\n`;
                }
              }
              if (recentOthers.length > 0) {
                display += others.length > 0 ? `---\n\n## Recently Active\n\n` : `## Recently Active\n\n`;
                for (const u of recentOthers.slice(0, 8)) {
                  display += `○ **@${u.handle}** — ${u.one_liner || 'Building something'}\n`;
                  display += `   _${formatTimeAgo(u.lastSeen)}_\n\n`;
                }
              }
              display += `Say "message @handle" to connect · "follow @handle" to add them`;
            }
            break;
          }
    
          case 'search': {
            if (!args.query) {
              return { display: 'Provide a search query: discover search "ai"' };
            }
            const q = args.query.toLowerCase();
            const matches = others.filter(u =>
              (u.note || u.one_liner || '').toLowerCase().includes(q) ||
              u.handle.toLowerCase().includes(q)
            );
    
            if (matches.length === 0) {
              display = `No one building "${args.query}" right now.`;
            } else {
              display = `## Building: "${args.query}"\n\n`;
              for (const u of matches) {
                display += `**@${u.handle}** — ${u.note || u.one_liner || 'Active'}\n`;
              }
            }
            break;
          }
    
          default:
            display = `## Discover Commands
    
    **\`discover suggest\`** — See who's building right now
    **\`discover search <query>\`** — Find people by what they're working on
    **\`discover active\`** — Same as suggest`;
        }
      } catch (error) {
        display = `Discovery error: ${error.message}`;
      }
    
      return { display };
    }
  • Exports the {definition, handler} module. Required by index.js line 173 as require('./tools/discover') and mapped to vibe_discover in the tools registry.
    /**
     * vibe discover — Find your people
     *
     * Smart matchmaking based on:
     * - What you're building (similar projects)
     * - What you've shipped (complementary skills)
     * - When you're active (timezone overlap)
     * - Shared interests (tags)
     *
     * Commands:
     * - discover suggest — Get personalized recommendations
     * - discover search <query> — Find people building specific things
     * - discover interests — Browse people by interest tags
     * - discover active — Show who's building similar things right now
     * - discover skills — Skills marketplace (absorbed from skills-exchange)
     * - discover partner — Find workshop partner (absorbed from workshop-buddy)
     */
    
    const config = require('../config');
    const store = require('../store');
    const { formatTimeAgo, requireInit } = require('./_shared');
    
    const definition = {
      name: 'vibe_discover',
      description: 'Find people building similar things. Commands: suggest, search, active.',
      inputSchema: {
        type: 'object',
        properties: {
          command: {
            type: 'string',
            enum: ['suggest', 'search', 'active'],
            description: 'Discovery command to run'
          },
          query: {
            type: 'string',
            description: 'Search query (for search command)'
          }
        }
      }
    };
    
    async function handler(args) {
      const initCheck = requireInit();
      if (initCheck) return initCheck;
    
      const myHandle = config.getHandle();
      const command = args.command || 'suggest';
    
      let display = '';
    
      try {
        // Get active users + recently active for richer discovery
        const users = await store.getActiveUsers({ includeRecent: true });
        const recentUsers = users._recent || [];
        const others = users.filter(u => u.handle !== myHandle);
        const recentOthers = recentUsers.filter(u => u.handle !== myHandle);
    
        switch (command) {
          case 'suggest':
          case 'active': {
            if (others.length === 0 && recentOthers.length === 0) {
              display = `## Discover
    
    _No one's been active recently. Be the first!_`;
            } else {
              if (others.length > 0) {
                display = `## Online Now\n\n`;
                for (const u of others) {
                  display += `**@${u.handle}**\n`;
                  display += `${u.note || u.one_liner || 'Building something'}\n`;
                  display += `_${formatTimeAgo(u.lastSeen)}_\n\n`;
                }
              }
              if (recentOthers.length > 0) {
                display += others.length > 0 ? `---\n\n## Recently Active\n\n` : `## Recently Active\n\n`;
                for (const u of recentOthers.slice(0, 8)) {
                  display += `○ **@${u.handle}** — ${u.one_liner || 'Building something'}\n`;
                  display += `   _${formatTimeAgo(u.lastSeen)}_\n\n`;
                }
              }
              display += `Say "message @handle" to connect · "follow @handle" to add them`;
            }
            break;
          }
    
          case 'search': {
            if (!args.query) {
              return { display: 'Provide a search query: discover search "ai"' };
            }
            const q = args.query.toLowerCase();
            const matches = others.filter(u =>
              (u.note || u.one_liner || '').toLowerCase().includes(q) ||
              u.handle.toLowerCase().includes(q)
            );
    
            if (matches.length === 0) {
              display = `No one building "${args.query}" right now.`;
            } else {
              display = `## Building: "${args.query}"\n\n`;
              for (const u of matches) {
                display += `**@${u.handle}** — ${u.note || u.one_liner || 'Active'}\n`;
              }
            }
            break;
          }
    
          default:
            display = `## Discover Commands
    
    **\`discover suggest\`** — See who's building right now
    **\`discover search <query>\`** — Find people by what they're working on
    **\`discover active\`** — Same as suggest`;
        }
      } catch (error) {
        display = `Discovery error: ${error.message}`;
      }
    
      return { display };
    }
    
    module.exports = { definition, handler };
  • index.js:36-36 (registration)
    Tool annotation registration: vibe_discover marked as readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true in TOOL_ANNOTATIONS.
    vibe_discover: { readOnlyHint: true,  destructiveHint: false, idempotentHint: true,  openWorldHint: true },
  • Prompt inference for logging: 'discover' command maps to 'discover ${args.command || "suggest"}' in inferPromptFromArgs.
    case 'discover': return `discover ${args.command || 'suggest'}`;
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the command enumeration but fails to explain what each command does or any behavioral traits like rate limits or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is very short (one sentence) but lacks structure. It lists commands without front-loading key details, and while concise, it sacrifices clarity.

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

Completeness2/5

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

Given no output schema and two parameters, the description is incomplete. It does not explain the purpose of each command, how to use them, or what the tool returns, leaving significant gaps for an AI agent.

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 coverage is 100%, so parameters are well-documented. The description merely reiterates the command enum without adding new meaning or usage context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as finding people building similar things, which is a clear verb+resource. It distinguishes from sibling tools like vibe_dm or vibe_ship through its function, though the command details are vague.

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 on when to use this tool versus alternatives. The commands (suggest, search, active) are listed but their specific uses or prerequisites are not explained, leaving the agent without context for selection.

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