Skip to main content
Glama
Sign In
DG-MCP

DG-MCP

by 0xNullAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

stop

Stop one or all channels of a DG-Lab Coyote device. Use to end output when user signals stop.

Instructions

【停止通道】停止一个通道，省略 channel 则停止全部通道。 触发：用户表达"停一下/够了/关掉"，或需要结束输出时。 不用：start(strength=0) 或其他变通方式不能代替 stop。 约束：无次数上限。

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": "stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNo要停止的通道，省略则停止全部。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations, so description carries full burden. It mentions no usage limit, but does not disclose if the action is destructive, reversible, or returns any status. Adds some value but insufficient for full transparency.

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?

Relatively short with front-loaded action. Could be slightly more concise but generally well-structured.

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?

Covers purpose, usage, trigger, and constraints, but given no output schema, it omits expected return behavior. Also lacks comparison with emergency_stop sibling.

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 the description repeats the schema's info about omitting channel stopping all. Description adds no new parameter semantics, so baseline 3 applies.

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

Purpose4/5

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

The description clearly states the tool stops a channel or all channels, with trigger conditions. However, it does not differentiate from the sibling tool 'emergency_stop', which might have similar purpose.

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?

Explicitly tells when to use (user says stop) and explicitly warns against using start(strength=0) as a substitute. Lacks comparison with other siblings like emergency_stop, but provides clear context.

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

Deploy Server

Other Tools