Skip to main content
Glama
suhitanantula

LLV Helix Framework

pulse_vibe

Send a pulse through a vibe to modulate its energy state. Specify amplitude and duration to shape the vibe's intensity over time.

Instructions

Send a pulse through a vibe

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vibe_nameYesName of the vibe
amplitudeNoPulse amplitude (0-1)
durationNoPulse duration in beats

Implementation Reference

  • The pulseVibe function that executes the pulse_vibe tool logic. It looks up the vibe by name, creates a pulse with amplitude/duration/frequency, stores it, and returns a formatted result.
    pulseVibe(args) {
      const { vibe_name, amplitude = 0.5, duration = 1 } = args;
      const vibe = this.vibes.get(vibe_name);
    
      if (!vibe) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ Vibe "${vibe_name}" not found.`,
            },
          ],
        };
      }
    
      const rhythm = this.rhythms.get(`vibe_${vibe_name}`);
      const pulse = {
        timestamp: new Date().toISOString(),
        amplitude,
        duration,
        frequency: vibe.frequency,
        rhythmStep: rhythm ? rhythm.next() : 1,
      };
    
      vibe.pulses.push(pulse);
    
      return {
        content: [
          {
            type: 'text',
            text: `✨ Pulsing vibe "${vibe_name}"\n\nEnergy: ${vibe.energy}\nAmplitude: ${(amplitude * 100).toFixed(0)}%\nDuration: ${duration} beats\n\n${this.visualizePulse(amplitude, vibe.frequency)}\n\nRhythm: ${vibe.rhythm} @ ${pulse.rhythmStep}`,
          },
        ],
      };
    }
  • The schema/definition for the pulse_vibe tool, including its name, description, and input schema with vibe_name (string, required), amplitude (number 0-1, optional), and duration (number, optional) properties.
    name: 'pulse_vibe',
    description: 'Send a pulse through a vibe',
    inputSchema: {
      type: 'object',
      properties: {
        vibe_name: {
          type: 'string',
          description: 'Name of the vibe',
        },
        amplitude: {
          type: 'number',
          minimum: 0,
          maximum: 1,
          description: 'Pulse amplitude (0-1)',
        },
        duration: {
          type: 'number',
          description: 'Pulse duration in beats',
        },
      },
      required: ['vibe_name'],
    },
  • index.js:343-344 (registration)
    The registration/case match that dispatches 'pulse_vibe' requests to the pulseVibe method.
    case 'pulse_vibe':
      return this.pulseVibe(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. 'Send a pulse' implies a transient effect, but there is no mention of side effects, permissions, rate limits, or whether the operation is read-only or destructive. This leaves significant behavioral gaps.

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 extremely concise at one sentence, but it fails to earn its place due to lack of informative content. While brevity is positive, it sacrifices necessary detail. The sentence could be expanded without losing conciseness.

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 the tool's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values, error conditions, or the overall behavior of the pulse action. A more complete description would include what happens after sending the pulse and how to use it in context.

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 covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond what is already in the schema. Since schema description coverage is high, a baseline of 3 is appropriate; the description does not enhance parameter understanding.

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

Purpose3/5

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

The description 'Send a pulse through a vibe' is a verb-noun pair but lacks specificity. It vaguely suggests an action without clarifying what 'pulse' means in this context, leaving room for ambiguity. Compared to siblings like 'compose_rhythm' or 'create_vibe', the purpose is somewhat distinguishable but not well-defined.

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 is provided on when to use this tool versus alternatives. There is no indication of prerequisites, appropriate scenarios, or exclusions. The description offers no help in deciding between 'pulse_vibe' and other tools like 'create_vibe' or 'compose_rhythm'.

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/suhitanantula/llv-helix'

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