Skip to main content
Glama

紧急停止

emergency_stop
DestructiveIdempotent

Instantly halt all movement and cut power for immediate safety. Returns confirmation; motion remains locked until an explicit unlock command.

Instructions

紧急停止 — 立即切断动力并锁定所有运动。返回确认信息。

此操作不可逆地锁定机械臂(destructiveHint=true)。锁定后所有运动指令被拒绝,直到调用 unlock 解除。与 stop 不同: stop 只是减速,不锁定,之后可以直接移动。用户说「停下!」「急停!」「STOP!」时应使用此工具。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint), the description discloses irreversible locking ('不可逆地锁定机械臂'), that all motion commands are rejected until unlock, and that a confirmation is returned. It also explicitly references destructiveHint=true, confirming consistency with annotations while adding recovery context.

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 compact and front-loaded: first sentence states the action and return, second explains the irreversible lock and recovery, third provides usage triggers and sibling contrast. Every sentence earns its place with no redundancy.

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 no parameters and an existing output schema, the description covers the tool's purpose, when to use it, its destructive/locking behavior, how to recover via unlock, and the sibling distinction. It is fully complete for an agent to select and invoke the tool correctly.

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?

There are zero parameters, so the schema fully covers them. The description adds no parameter-specific semantics, but the baseline of 4 for zero-parameter tools applies because no additional parameter explanation is needed.

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 verb+resource: '立即切断动力并锁定所有运动' (immediately cut power and lock all motion), and explicitly distinguishes it from the sibling tool 'stop' by noting 'stop 只是减速,不锁定' (stop only decelerates, does not lock). This clearly defines the tool's unique purpose.

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?

It provides explicit when-to-use guidance: '用户说「停下!」「急停!」「STOP!」时应使用此工具' (use this tool when the user says stop/emergency stop), and contrasts with the alternative 'stop' by explaining that stop does not lock and allows immediate movement. It also mentions the unlock requirement, giving the agent a clear decision path.

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/HBConline/HLORO-AI'

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