Skip to main content
Glama
0xNullAI

DG-MCP

by 0xNullAI

start

Start a channel on a DG-LAB Coyote device by setting initial intensity (0-10) and waveform. Choose from breath, tide, pulse, or tap patterns to begin stimulation.

Instructions

【启动通道】启动一个通道,同时设置初始强度和波形。 触发:通道当前停止,需要从零开始时使用。 不用:通道已运行 → 想加点强度用 adjust_strength,想换波形用 change_wave,想结束用 stop。 约束:单次启动强度上限 10(受安全设置约束),完成后先描述结果并询问感受,不要在同一回合连续追加多次强度。 可用波形:breath(呼吸:渐强渐弱,最温柔的铺垫波形);tide(潮汐:波浪般起伏的慢节奏);pulse_low(低脉冲:轻柔的规律节奏);pulse_mid(中脉冲:中等强度的规律节奏);pulse_high(高脉冲:强烈的规律节奏);tap(敲击:带节奏停顿的点触感)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes通道 A 或 B
strengthYes启动时的初始强度,范围 [0, 10]。
waveformIdYes波形 ID - breath(呼吸:渐强渐弱,最温柔的铺垫波形);tide(潮汐:波浪般起伏的慢节奏);pulse_low(低脉冲:轻柔的规律节奏);pulse_mid(中脉冲:中等强度的规律节奏);pulse_high(高脉冲:强烈的规律节奏);tap(敲击:带节奏停顿的点触感)
loopNo是否循环播放波形,默认 true。
Behavior5/5

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

With no annotations, the description fully discloses behavioral constraints: strength max 10 (safety), post-completion actions (describe result, ask feeling), and prevention of escalation. Also lists available waveforms with descriptions.

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

Conciseness4/5

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

Well-structured with sections for trigger, usage, constraints, and waveforms. Information is front-loaded. Slightly long but every sentence is useful; could be slightly condensed without losing clarity.

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

Completeness5/5

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

Given the tool's complexity (4 params, 3 required, 2 enums, no output schema), the description covers purpose, usage, constraints, and waveform details comprehensively. No gaps for an agent to misuse.

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%, so parameters are well-documented. The description adds value by explaining behavioral context like the strength constraint and post-completion steps, enhancing understanding 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 starts a channel with initial strength and waveform. It distinguishes from siblings like adjust_strength, change_wave, and stop, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly provides when to use (channel stopped) and when not to use (channel running), naming alternative tools. This offers clear guidance for tool 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/0xNullAI/DG-MCP'

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