Skip to main content
Glama

vibe_ship

Announce your shipped project to the community board and update your profile with a description, URL, and tags. Fulfill requests or credit inspirations.

Instructions

Announce something you just shipped to the community board and update your profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whatYesWhat you shipped (brief description)
urlNoURL to your ship (deployed site, repo, demo)
inspired_byNoHandle of person who inspired this (@alice)
for_requestNoRequest ID this fulfills (if building for someone)
tagsNoTags for discovery (e.g., ["ai", "mcp", "tools"])

Implementation Reference

  • The main handler function for vibe_ship. It validates args, builds rich content with metadata (URL, inspired_by, for_request), POSTs to /api/board, and returns a formatted display with a shareable tweet.
    async function handler(args) {
      const initCheck = requireInit();
      if (initCheck) return initCheck;
    
      if (!args.what) {
        return { error: 'Please tell us what you shipped: ship "Built a new feature"' };
      }
    
      const myHandle = config.getHandle();
      const apiUrl = config.getApiUrl();
    
      try {
        // Build rich content with metadata
        let content = args.what;
        const metaParts = [];
    
        if (args.url) {
          metaParts.push(`šŸ”— ${args.url}`);
        }
        if (args.inspired_by) {
          const inspiree = args.inspired_by.replace('@', '').toLowerCase();
          metaParts.push(`✨ inspired by @${inspiree}`);
        }
        if (args.for_request) {
          metaParts.push(`šŸ“‹ fulfills ${args.for_request}`);
        }
    
        if (metaParts.length > 0) {
          content += '\n' + metaParts.join(' | ');
        }
    
        // Build tags with attribution
        const tags = args.tags || [];
        if (args.inspired_by) {
          tags.push(`inspired:${args.inspired_by.replace('@', '')}`);
        }
        if (args.for_request) {
          tags.push(`fulfills:${args.for_request}`);
        }
    
        // Post to board
        const response = await fetch(`${apiUrl}/api/board`, {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify({
            author: myHandle,
            content,
            category: 'shipped',
            tags
          })
        });
    
        const data = await response.json();
    
        if (!data.success) {
          return { display: `āš ļø Failed to announce ship: ${data.error}` };
        }
    
        let display = `šŸš€ shipped\n\n${args.what}`;
    
        if (args.url) {
          display += `\n${args.url}`;
        }
        if (args.inspired_by) {
          display += `\n_via @${args.inspired_by.replace('@', '')}_`;
        }
    
        // Generate share-ready tweet
        const tweetParts = [`Just shipped: ${args.what} šŸš€`];
        if (args.url) tweetParts.push(args.url);
        tweetParts.push('#vibecoding');
        const tweet = tweetParts.join(' ');
    
        display += `\n\n---\nšŸ“‹ **Share it:**\n\`${tweet}\``;
    
        return { display };
    
      } catch (error) {
        return { display: `## Ship Error\n\n${error.message}` };
      }
    }
  • The tool definition/schema for vibe_ship, defining the name, description, and inputSchema with properties: what (required), url, inspired_by, for_request, and tags.
    const definition = {
      name: 'vibe_ship',
      description: 'Announce something you just shipped to the community board and update your profile.',
      inputSchema: {
        type: 'object',
        properties: {
          what: {
            type: 'string',
            description: 'What you shipped (brief description)'
          },
          url: {
            type: 'string',
            description: 'URL to your ship (deployed site, repo, demo)'
          },
          inspired_by: {
            type: 'string',
            description: 'Handle of person who inspired this (@alice)'
          },
          for_request: {
            type: 'string',
            description: 'Request ID this fulfills (if building for someone)'
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'Tags for discovery (e.g., ["ai", "mcp", "tools"])'
          }
        },
        required: ['what']
      }
    };
  • index.js:165-175 (registration)
    Registration of vibe_ship in the tools map: requiring './tools/ship' and mapping it to the 'vibe_ship' key.
    const tools = {
      vibe_start: require('./tools/start'),
      vibe_init: require('./tools/init'),
      vibe_who: require('./tools/who'),
      vibe_dm: require('./tools/dm'),
      vibe_inbox: require('./tools/inbox'),
      vibe_status: require('./tools/status'),
      vibe_ship: require('./tools/ship'),
      vibe_discover: require('./tools/discover'),
      vibe_help: require('./tools/help'),
    };
  • index.js:35-38 (registration)
    Safety annotations for vibe_ship: readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true.
      vibe_ship:     { readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: true },
      vibe_discover: { readOnlyHint: true,  destructiveHint: false, idempotentHint: true,  openWorldHint: true },
      vibe_help:     { readOnlyHint: true,  destructiveHint: false, idempotentHint: true,  openWorldHint: false },
    };
  • index.js:271-277 (registration)
    vibe_ship is listed as a state-changing tool that triggers list_changed notifications after execution.
    const stateChangingTools = [
      'vibe_dm', 'vibe_status', 'vibe_ship'
    ];
    if (stateChangingTools.includes(params.name)) {
      // Debounced notification (prevents spam)
      global.vibeNotifier?.emitChange(params.name);
    }
Behavior3/5

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

The description states it updates the profile, adding context beyond the annotations that declare readOnlyHint=false. However, it does not disclose details about side effects, auth requirements, or rate limits, so it adds only marginal value.

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, clear sentence of 13 words. It is appropriately sized and front-loaded, with no wasted words.

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 the number of parameters and annotations, the description is minimally complete. It covers the high-level purpose but lacks details on return values, how the community board works, or any additional context that might help an agent invoke the tool correctly.

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 100% description coverage for all parameters, so the tool description does not need to add extra meaning. It meets the baseline but does not enhance understanding of parameters 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?

The description clearly states the tool announces something shipped to a community board and updates the user's profile. It uses a specific verb 'announce' and identifies the resource, distinguishing it from sibling tools like vibe_discover or vibe_start.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. This leaves the agent without context to distinguish from sibling tools beyond the name.

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