vibe

vibe_start

Initiate a social session to connect with other developers, share what you're building, and see who's around for collaboration.

Instructions

Start socializing on /vibe. Use when user says "let's vibe", "start vibing", "who's around", or wants to connect with others.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vibe_start"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	No	Your handle (use your X/Twitter handle). Only needed if not already initialized.
`building`	No	What you're working on (one line). Only needed if not already initialized.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.10Mar 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It merely says 'Start socializing' without explaining side effects, whether it requires prior initialization (though the schema hints at this), what the tool does to the system, or what the user experiences. Critical behavioral context is missing.

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 two sentences with zero waste. Trigger phrases are front-loaded, and it is easy to scan quickly. Every word serves a purpose.

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?

For a tool with no output schema and no annotations, the description should explain the initialization requirement, what happens after the call, and how it relates to sibling tools. It only covers the trigger context, leaving significant gaps about preconditions and effects.

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% and both parameters have clear descriptions in the schema. The description itself adds no parameter-level detail beyond what the schema already provides, so a baseline score 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?

The description states a specific action ('Start socializing on /vibe') and provides concrete trigger phrases ('let's vibe', 'start vibing') that map to user intents. It clearly distinguishes itself from siblings like vibe_init (initialization) and vibe_who (checking who's around) by focusing on the act of starting a social session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists when to use the tool with example user statements, giving clear context for invocation. However, it does not mention alternatives or when NOT to use it, leaving some ambiguity with sibling tools like vibe_who that might also handle 'who's around' queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server