Skip to main content
Glama
VibeCodingInc

vibe

by VibeCodingInc
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript

vibe_status

Set your current mood or status and manage notification pace for team collaboration.

Instructions

Set your mood/status, or your notification pace. Mood: shipping, thinking, afk, debugging, pairing, deep, celebrating, struggling, away, back, clear. Pace: slower (only ping when away), quiet (no pushes), normal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moodYesA mood (shipping, thinking, afk, debugging, pairing, deep, celebrating, struggling, away, back, clear) OR a notification pace (slower, quiet, normal)
messageNoOptional away message (only used with away mood, e.g., "grabbing coffee")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.18
    • addedInput schema / properties / message
      Added value: +{
+  "description": "Optional away message (only used with away mood, e.g., \"grabbing coffee\")",
+  "type": "string"
+}
    • changedInput schema / properties / mood / description
      Previous value: -"Your mood (shipping, thinking, afk, debugging, pairing, deep, celebrating, struggling, clear)"New value: +"A mood (shipping, thinking, afk, debugging, pairing, deep, celebrating, struggling, away, back, clear) OR a notification pace (slower, quiet, normal)"
  2. First observedv0.4.10

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the behavioral consequences of pace values (when pings occur, push notifications) and notes the message is only for away mood (also in schema). However, it does not mention persistence, visibility to others, or whether setting a mood overwrites existing status, which are relevant but not critical for a basic call.

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, tightly written sentence that front-loads the action and then efficiently lists all value options. No wasted words, and the structure supports quick scanning.

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?

For a simple two-parameter tool with no output schema or annotations, the description provides sufficient detail to call it correctly: it explains mood vs pace, the effect of pace, and the message constraint is in the schema. Minor omissions like side effects or persistence do not impair a correct first call.

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?

Schema coverage is 100% with both parameters described, giving a baseline of 3. The description adds value by explaining the effect of each pace option (e.g., 'slow only pings when away', 'quiet no pushes'), which goes beyond the schema's list of values and helps the agent choose appropriately.

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 clear verb ('Set') and resource ('your mood/status, or your notification pace'), and enumerates the specific values for both. This distinguishes it from sibling tools like vibe_dm (messaging) or vibe_inbox (reading messages) by focusing on self-status management.

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 explains the two modes (mood vs pace) and their effects (e.g., 'slower only ping when away', 'quiet no pushes'), which provides internal usage guidance. However, it does not explicitly mention when to prefer this tool over siblings or when not to use it, leaving the selection largely implicit.

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